BIZTRAC BETA
Rental and operating of own or leased real estate

RESORT INVEST AS

Org. no. 998534623 Limited company (AS) Kragerø Incorporated 2012 Active
Ownership graph ↗
Revenue 2024 NOK 9.2m
Operating profit NOK −4.2m
Equity NOK 19.2m
Incorporated 2012
Share capital NOK 230,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−4,2 mill kr).

RESORT INVEST AS is registered as a limited company in Kragerø, Telemark with organisation number 998534623. 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 230,000, divided into 230300 shares. The company's stated purpose is: “Forvaltning av selskapets kapital gjennom kjøp og salg av aksjer, selskaper og andre formuesverdier, herunder deltakelse i andre selskaper med lignende virksomhet eller på annen måte gjøre seg interessert i andre foretagender.”. The most recent filed accounts, for the 2024 financial year, show NOK 9.2m in revenue and NOK −4.2m in operating profit.

Key figures · 2024

Revenue
NOK 9.2m
Operating profit
NOK −4.2m
Equity
NOK 19.2m
Est. value
NOK 26.7m

Financial health · 2024

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

Who owns RESORT INVEST AS?

KRAGERØ RESORT UTVIKLING AS
RESORT INVEST AS
NOK 9.2m rev. · NOK −4.2m profit

RESORT INVEST AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about RESORT INVEST AS

Who owns RESORT INVEST AS?

KRAGERØ RESORT UTVIKLING AS is the largest registered owner, with 100.0%.

What is the revenue of RESORT INVEST AS?

RESORT INVEST AS had revenue of NOK 9.2m in 2024.

Where is RESORT INVEST AS based?

RESORT INVEST AS has its business address in Stabbestad.

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.