BIZTRAC BETA
Rental and operating of own or leased real estate

AS FAGERBORGGATEN 42

Org. no. 921524099 Limited company (AS) Oslo Incorporated 1934 Active
Ownership graph ↗
Revenue 2024 NOK 3.9m
Operating profit NOK 2.8m
Equity NOK 8.4m
Incorporated 1934
Share capital NOK 110,000

Signals

2 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.
  • Nylig endring 2026-07-16 Adresseendring registrert 2026-07-16.

AS FAGERBORGGATEN 42 is registered as a limited company in Oslo, Oslo with organisation number 921524099. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 1934. Registered share capital is NOK 110,000, divided into 44 shares. The company's stated purpose is: “Eie, utvikle og drifte Fagerborggaten 42 AS i Oslo og annen virksomhet som står i forbindelse med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 3.9m in revenue and NOK 2.8m in operating profit.

Key figures · 2024

Revenue
NOK 3.9m
Operating profit
NOK 2.8m
Equity
NOK 8.4m
Est. value
NOK 11.5m

Financial health · 2024

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

Who owns AS FAGERBORGGATEN 42?

GONDROSEN HOLDING AS
AS FAGERBORGGATEN 42
NOK 3.9m rev. · NOK 2.8m profit

AS FAGERBORGGATEN 42 has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about AS FAGERBORGGATEN 42

Who owns AS FAGERBORGGATEN 42?

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

What is the revenue of AS FAGERBORGGATEN 42?

AS FAGERBORGGATEN 42 had revenue of NOK 3.9m in 2024.

Where is AS FAGERBORGGATEN 42 based?

AS FAGERBORGGATEN 42 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.