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

OLASKJÆRET AS

Org. no. 995850575 Limited company (AS) Alstahaug Incorporated 2010 Active
Ownership graph ↗
Revenue 2025 NOK 682,000
Operating profit NOK 243,000
Equity NOK 2.2m
Incorporated 2010
Share capital NOK 100,000

OLASKJÆRET AS is registered as a limited company in Alstahaug, Nordland with organisation number 995850575. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2010. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Eie og utvikle eiendom, anlegg og driftsmidler samt forestå utleie og drift av disse. Videre kan selskapet eie aksjer og andeler i andre foretak.”. The most recent filed accounts, for the 2025 financial year, show NOK 682,000 in revenue and NOK 243,000 in operating profit.

Key figures · 2025

Revenue
NOK 682,000
▲ +2 %
Operating profit
NOK 243,000
▼ −12 %
Equity
NOK 2.2m
▲ +5 %
Est. value
NOK 2.1m

Financial health · 2025

Liquidity
7.45
Very good
Current assets ÷ current liabilities
Profitability
7.1%
Satisfactory
Return on total assets
Solidity
64.1%
Very good
Equity as a share of total capital

Who owns OLASKJÆRET AS?

OLASKJÆRET AS
NOK 682,000 rev. · NOK 243,000 profit

OLASKJÆRET AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about OLASKJÆRET AS

Who owns OLASKJÆRET AS?

CINETT AS is the largest registered owner, with 82.0%.

What is the revenue of OLASKJÆRET AS?

OLASKJÆRET AS had revenue of NOK 682,000 in 2025.

Who is the general manager of OLASKJÆRET AS?

Geir Åsberg is registered as general manager of OLASKJÆRET AS.

Where is OLASKJÆRET AS based?

OLASKJÆRET AS has its business address in Sandnessjøen.

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.