BIZTRAC BETA
Landscape service activities

M PARK - ANLEGG AS

Org. no. 981481984 Limited company (AS) Skien Incorporated 1999 Active
Ownership graph ↗
Revenue 2025 NOK 948,000
Operating profit NOK 223,000
Equity NOK 48,000
Incorporated 1999
Share capital NOK 100,000

M PARK - ANLEGG AS is registered as a limited company in Skien, Telemark with organisation number 981481984. The business is classified under landscape service activities (NACE 81.300). The company was incorporated in 1999. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Plenklipping, vedlikehold av fotballbaner, snøbrøyting, sandstrøing, belegningsstein, gartnerarbeid, graving, transport, oppussing av bygning med interiørtjenester, m.m.”. The most recent filed accounts, for the 2025 financial year, show NOK 948,000 in revenue and NOK 223,000 in operating profit.

Key figures · 2025

Revenue
NOK 948,000
Operating profit
NOK 223,000
Equity
NOK 48,000
Est. value
NOK 717,000

Financial health · 2025

Liquidity
1.03
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
44.4%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns M PARK - ANLEGG AS?

MEMRUR SUKALIC
M PARK - ANLEGG AS
NOK 948,000 rev. · NOK 223,000 profit

M PARK - ANLEGG AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about M PARK - ANLEGG AS

Who owns M PARK - ANLEGG AS?

MEMRUR SUKALIC is the largest registered owner, with 100.0%.

What is the revenue of M PARK - ANLEGG AS?

M PARK - ANLEGG AS had revenue of NOK 948,000 in 2025.

Who is the general manager of M PARK - ANLEGG AS?

Memrur Sukalic is registered as general manager of M PARK - ANLEGG AS.

Where is M PARK - ANLEGG AS based?

M PARK - ANLEGG AS has its business address in Skien.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 15.06.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.