BIZTRAC BETA
Rental and operating of own or leased real estate

PARKVEIEN NÆRING AS

Org. no. 927378299 Limited company (AS) Oslo Incorporated 2021 Active
Ownership graph ↗
Revenue 2025 NOK 845,000
Operating profit NOK 409,000
Equity NOK 1.2m
Incorporated 2021
Share capital NOK 170,000

Signals

1 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

PARKVEIEN NÆRING AS is registered as a limited company in Oslo, Oslo with organisation number 927378299. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2021. Registered share capital is NOK 170,000, divided into 169918 shares. The company's stated purpose is: “Drift og utleie av fast eiendom, investeringer og alt som står i forbindelse med dette, herunder å eie aksjer og andeler i andre virksomheter og selskaper.”. The most recent filed accounts, for the 2025 financial year, show NOK 845,000 in revenue and NOK 409,000 in operating profit.

Key figures · 2025

Revenue
NOK 845,000
Operating profit
NOK 409,000
Equity
NOK 1.2m
Est. value
NOK 1.8m

Financial health · 2025

Liquidity
0.24
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
24.7%
Good
Equity as a share of total capital

Who owns PARKVEIEN NÆRING AS?

MM10 HOLDING AS
PARKVEIEN NÆRING AS
NOK 845,000 rev. · NOK 409,000 profit

PARKVEIEN NÆRING AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about PARKVEIEN NÆRING AS

Who owns PARKVEIEN NÆRING AS?

MM10 HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of PARKVEIEN NÆRING AS?

PARKVEIEN NÆRING AS had revenue of NOK 845,000 in 2025.

Where is PARKVEIEN NÆRING AS based?

PARKVEIEN NÆRING AS has its business address in Oslo.

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.