BIZTRAC BETA
Rental and operating of own or leased real estate

GJERDRUMS VEI 9 AS

Org. no. 990589682 Limited company (AS) Oslo Incorporated 2006 Active
Ownership graph ↗
Revenue 2024 NOK 128.4m
Operating profit NOK 27.5m
Equity NOK 13.9m
Incorporated 2006
Share capital NOK 100,000

Signals

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

GJERDRUMS VEI 9 AS is registered as a limited company in Oslo, Oslo with organisation number 990589682. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2006. Registered share capital is NOK 100,000, divided into 100000 shares. The company's stated purpose is: “Å investere i fast eiendom eller selskaper som eier fast eiendom, og alt som dermed står i forbindelse.”. The most recent filed accounts, for the 2024 financial year, show NOK 128.4m in revenue and NOK 27.5m in operating profit.

Key figures · 2024

Revenue
NOK 128.4m
Operating profit
NOK 27.5m
Equity
NOK 13.9m
Est. value
NOK 78.7m

Financial health · 2024

Liquidity
2.26
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
55.8%
Very good
Equity as a share of total capital

Who owns GJERDRUMS VEI 9 AS?

NYDALEN AS
GJERDRUMS VEI 9 AS
NOK 128.4m rev. · NOK 27.5m profit

GJERDRUMS VEI 9 AS has 1 registered shareholder:

All shareholders and roles →

Group structure

GJERDRUMS VEI 9 AS er morselskap for 36 datterselskaper:

Frequently asked questions about GJERDRUMS VEI 9 AS

Who owns GJERDRUMS VEI 9 AS?

NYDALEN AS is the largest registered owner, with 100.0%.

What is the revenue of GJERDRUMS VEI 9 AS?

GJERDRUMS VEI 9 AS had revenue of NOK 128.4m in 2024.

Where is GJERDRUMS VEI 9 AS based?

GJERDRUMS VEI 9 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.