BIZTRAC BETA
Rental and operating of own or leased real estate

KRISTIAN AUGUSTS GATE 13 AS

Org. no. 918341013 Limited company (AS) Oslo Incorporated 2016 Active
Ownership graph ↗
Revenue 2024 NOK 12.0m
Operating profit NOK 4.9m
Equity NOK 64.4m
Incorporated 2016
Share capital NOK 591,000

Signals

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

KRISTIAN AUGUSTS GATE 13 AS is registered as a limited company in Oslo, Oslo with organisation number 918341013. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2016. Registered share capital is NOK 591,000, divided into 591 shares. The company's stated purpose is: “Investere i, drive og utvikle 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 12.0m in revenue and NOK 4.9m in operating profit.

Key figures · 2024

Revenue
NOK 12.0m
Operating profit
NOK 4.9m
Equity
NOK 64.4m
Est. value
NOK 51.4m

Financial health · 2024

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

Who owns KRISTIAN AUGUSTS GATE 13 AS?

ENTRA ASA
KRISTIAN AUGUSTS GATE 13 AS
NOK 12.0m rev. · NOK 4.9m profit

KRISTIAN AUGUSTS GATE 13 AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about KRISTIAN AUGUSTS GATE 13 AS

Who owns KRISTIAN AUGUSTS GATE 13 AS?

ENTRA ASA is the largest registered owner, with 100.0%.

What is the revenue of KRISTIAN AUGUSTS GATE 13 AS?

KRISTIAN AUGUSTS GATE 13 AS had revenue of NOK 12.0m in 2024.

Where is KRISTIAN AUGUSTS GATE 13 AS based?

KRISTIAN AUGUSTS GATE 13 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.