BIZTRAC BETA
Rental and operating of own or leased real estate

MEL GARDERMOEN 2 AS

Org. no. 828323202 Limited company (AS) Nannestad Incorporated 2021 Active
Ownership graph ↗
Revenue 2024 NOK 60,000
Operating profit NOK −33,000
Equity NOK −85,000
Incorporated 2021
Share capital NOK 32,000

Signals

2 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−85k kr).
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−33k kr).

MEL GARDERMOEN 2 AS is registered as a limited company in Nannestad, Akershus with organisation number 828323202. 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 32,000, divided into 100 shares. The company's stated purpose is: “Drift eller utleie av egen fast eiendom og hva dermed står i forbindelse.”. The most recent filed accounts, for the 2024 financial year, show NOK 60,000 in revenue and NOK −33,000 in operating profit.

Key figures · 2024

Revenue
NOK 60,000
Operating profit
NOK −33,000
Equity
NOK −85,000

Financial health · 2024

Liquidity
0.10
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-11.2%
Weak
Equity as a share of total capital

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

Who owns MEL GARDERMOEN 2 AS?

No shareholders are registered for MEL GARDERMOEN 2 AS in open Norwegian sources. Shareholder data exists mainly for limited companies (AS/ASA).

Frequently asked questions about MEL GARDERMOEN 2 AS

What is the revenue of MEL GARDERMOEN 2 AS?

MEL GARDERMOEN 2 AS had revenue of NOK 60,000 in 2024.

Who is the general manager of MEL GARDERMOEN 2 AS?

Cato Brynildsen is registered as general manager of MEL GARDERMOEN 2 AS.

Where is MEL GARDERMOEN 2 AS based?

MEL GARDERMOEN 2 AS has its business address in Nannestad.

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.