BIZTRAC BETA
Rental and operating of own or leased real estate

KRONHJORTEN AS

Org. no. 989035916 Limited company (AS) Oslo Incorporated 2005 Active
Ownership graph ↗
Revenue 2024 NOK 75,000
Operating profit NOK 3,000
Equity NOK 2.9m
Incorporated 2005
Share capital NOK 200,000

Signals

1 flags
  • Nylig endring 2026-06-29 Adresseendring registrert 2026-06-29.

KRONHJORTEN AS is registered as a limited company in Oslo, Oslo with organisation number 989035916. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2005. Registered share capital is NOK 200,000, divided into 2000 shares. The company's stated purpose is: “Investering i aksjer, eiendom, drift og omsetnings- og finansieringsvirksomhet samt enhver for dette formål nødvendig virksomhet, videre konsultativ og managementrettet virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 75,000 in revenue and NOK 3,000 in operating profit.

Key figures · 2024

Revenue
NOK 75,000
Operating profit
NOK 3,000
Equity
NOK 2.9m
Est. value
NOK 2.0m

Financial health · 2024

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

Who owns KRONHJORTEN AS?

GEIR HJORTH
KRONHJORTEN AS
NOK 75,000 rev. · NOK 3,000 profit

KRONHJORTEN AS has 2 registered shareholders:

All shareholders and roles →

Which companies does KRONHJORTEN AS own?

KRONHJORTEN AS holds stakes in 4 companies:

See the full ownership structure →

Frequently asked questions about KRONHJORTEN AS

Who owns KRONHJORTEN AS?

GEIR HJORTH is the largest registered owner, with 80.0%.

What is the revenue of KRONHJORTEN AS?

KRONHJORTEN AS had revenue of NOK 75,000 in 2024.

Where is KRONHJORTEN AS based?

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