BIZTRAC BETA
Rental and operating of own or leased real estate

KONGENS GATE 18 AS

Org. no. 998827116 Limited company (AS) Oslo Incorporated 2012 Active
Ownership graph ↗
Revenue 2024 NOK 845,000
Operating profit NOK 447,000
Equity NOK 110,000
Incorporated 2012
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.

KONGENS GATE 18 AS is registered as a limited company in Oslo, Oslo with organisation number 998827116. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2012. Registered share capital is NOK 100,000, divided into 1000 shares. The company's stated purpose is: “Kjøp og drift av faste eiendommer, samt kjøp, drift og økonomisk interesse i andre bedrifter og virksomheter og hva dermed står i forbindelse med.”. The most recent filed accounts, for the 2024 financial year, show NOK 845,000 in revenue and NOK 447,000 in operating profit.

Key figures · 2024

Revenue
NOK 845,000
Operating profit
NOK 447,000
Equity
NOK 110,000
Est. value
NOK 1.1m

Financial health · 2024

Liquidity
0.69
Weak
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
10.9%
Satisfactory
Equity as a share of total capital

Who owns KONGENS GATE 18 AS?

CLARENCE JENSEN EIENDOM AS
KONGENS GATE 18 AS
NOK 845,000 rev. · NOK 447,000 profit

KONGENS GATE 18 AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about KONGENS GATE 18 AS

Who owns KONGENS GATE 18 AS?

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

What is the revenue of KONGENS GATE 18 AS?

KONGENS GATE 18 AS had revenue of NOK 845,000 in 2024.

Where is KONGENS GATE 18 AS based?

KONGENS GATE 18 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.