biztrac. BETA
COMPANY REGISTER PROFILE
990589682 ORG. NO. 2025 ACCOUNTS 9 SECTIONS
Active UPDATED 03.10.2026
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 2025 NOK 14,000
Operating profit NOK 72,000
Equity NOK 100,000
Incorporated 2006
Share capital NOK 100,000

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 2025 financial year, show NOK 14,000 in revenue and NOK 72,000 in operating profit.

Former names: AVANTOR GJERDRUMS VEI 9 AS

Key figures · 2025

Revenue
NOK 14,000
▼ −100 %
Operating profit
NOK 72,000
▼ −100 %
Equity
NOK 100,000
▼ −99 %
Est. value
NOK 14.6m

Financial health · 2025

Liquidity
1.26
Satisfactory
Current assets ÷ current liabilities
Profitability
4.4%
Weak
Return on total assets
Solidity
0.4%
Not satisfactory
Equity as a share of total capital

Who owns GJERDRUMS VEI 9 AS?

GJERDRUMS VEI 9 AS
NOK 14,000 rev. · NOK 72,000 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 14,000 in 2025.

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 03.10.2026.

Report a problem

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