biztrac. BETA
COMPANY REGISTER PROFILE
846860282 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Rental and operating of own or leased real estate

RAVNÅS EIENDOM AS

Org. no. 846860282 Limited company (AS) Holmestrand Incorporated 1988 Active
Revenue 2025 NOK 50,000
Operating profit NOK −100,000
Equity NOK 3.5m
Incorporated 1988
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−100k kr).

RAVNÅS EIENDOM AS is registered as a limited company in Holmestrand, Vestfold with organisation number 846860282. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 1988. Registered share capital is NOK 30,000, divided into 250 shares. The company's stated purpose is: “Utleie av fast eiendom, utleie av driftsmidler, kjøp og salg av båter samt å delta i andre selskaper.”. The most recent filed accounts, for the 2025 financial year, show NOK 50,000 in revenue and NOK −100,000 in operating profit.

Former names: RAVNÅS & CO A/S

Key figures · 2025

Revenue
NOK 50,000
▲ +35 %
Operating profit
NOK −100,000
▼ −22 %
Equity
NOK 3.5m
▼ −0 %
Est. value
NOK 2.5m

Financial health · 2025

Liquidity
–
Not available
Current assets ÷ current liabilities
Profitability
-0.9%
Not satisfactory
Return on total assets
Solidity
85.0%
Very good
Equity as a share of total capital

Who owns RAVNÅS EIENDOM AS?

RAVNÅS EIENDOM AS
NOK 50,000 rev. · NOK −100,000 profit

RAVNÅS EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about RAVNÅS EIENDOM AS

Who owns RAVNÅS EIENDOM AS?

Vidar Ravnås is the largest registered owner, with 100.0%.

What is the revenue of RAVNÅS EIENDOM AS?

RAVNÅS EIENDOM AS had revenue of NOK 50,000 in 2025.

Where is RAVNÅS EIENDOM AS based?

RAVNÅS EIENDOM AS has its business address in Holmestrand.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.