BIZTRAC BETA
Rental and operating of own or leased real estate

GRØNNEGATA 122 AS

Org. no. 913013409 Limited company (AS) Oslo Incorporated 2013 Active
Ownership graph ↗
Revenue 2024 NOK 13.3m
Operating profit NOK 8.1m
Equity NOK 19.5m
Incorporated 2013
Share capital NOK 500,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-06-04 Adresseendring registrert 2026-06-04.

GRØNNEGATA 122 AS is registered as a limited company in Oslo, Oslo with organisation number 913013409. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2013. Registered share capital is NOK 500,000, divided into 1 shares. The company's stated purpose is: “Drive virksomhet innenfor utvikling og investering i andre selskaper og alt som står i forbindelse med de forannevnte virksomheter.”. The most recent filed accounts, for the 2024 financial year, show NOK 13.3m in revenue and NOK 8.1m in operating profit.

Key figures · 2024

Revenue
NOK 13.3m
Operating profit
NOK 8.1m
Equity
NOK 19.5m
Est. value
NOK 26.0m

Financial health · 2024

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

Who owns GRØNNEGATA 122 AS?

OFFENTLIG EIENDOM AS
GRØNNEGATA 122 AS
NOK 13.3m rev. · NOK 8.1m profit

GRØNNEGATA 122 AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about GRØNNEGATA 122 AS

Who owns GRØNNEGATA 122 AS?

OFFENTLIG EIENDOM AS is the largest registered owner, with 100.0%.

What is the revenue of GRØNNEGATA 122 AS?

GRØNNEGATA 122 AS had revenue of NOK 13.3m in 2024.

Where is GRØNNEGATA 122 AS based?

GRØNNEGATA 122 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.