BIZTRAC BETA
Rental and operating of own or leased real estate

OLAVSEN AS

Org. no. 964387354 Limited company (AS) Vestvågøy Incorporated 1992 Active
Ownership graph ↗
Revenue 2024 NOK 945,000
Operating profit NOK −1.2m
Equity NOK −224,000
Incorporated 1992
Share capital NOK 1.2m

Signals

3 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−224k kr).
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−1,2 mill kr).
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

OLAVSEN AS is registered as a limited company in Vestvågøy, Nordland with organisation number 964387354. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 1992. Registered share capital is NOK 1.2m, divided into 1200 shares. The company's stated purpose is: “Eie, forvalte og utleie av fast eiendom samt det som står i forbindelse hermed.”. The most recent filed accounts, for the 2024 financial year, show NOK 945,000 in revenue and NOK −1.2m in operating profit.

Key figures · 2024

Revenue
NOK 945,000
Operating profit
NOK −1.2m
Equity
NOK −224,000

Financial health · 2024

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

Solidity capped at Weak because equity is below NOK 100,000.

Who owns OLAVSEN AS?

GRAFO AS
OLAVSEN AS
NOK 945,000 rev. · NOK −1.2m profit

OLAVSEN AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about OLAVSEN AS

Who owns OLAVSEN AS?

GRAFO AS is the largest registered owner, with 100.0%.

What is the revenue of OLAVSEN AS?

OLAVSEN AS had revenue of NOK 945,000 in 2024.

Where is OLAVSEN AS based?

OLAVSEN AS has its business address in Stamsund.

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.