BIZTRAC BETA
Site preparation

OLIMB HOLDING AS

Org. no. 897378302 Limited company (AS) Råde Incorporated 2011 Active
Ownership graph ↗
Operating profit NOK −299,000
Equity NOK 140.1m
Incorporated 2011
Share capital NOK 4.0m

Signals

2 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−299k kr).
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

OLIMB HOLDING AS is registered as a limited company in Råde, Østfold with organisation number 897378302. The business is classified under site preparation (NACE 43.120). The company was incorporated in 2011. Registered share capital is NOK 4.0m, divided into 4024972 shares. The company's stated purpose is: “Entreprenørvirksomhet og hva dermed står i forbindelse, herunder deltagelse i andre selskaper. Selskapets formål er også å kunne dele ut midler til veldedige formål.”.

Key figures · 2024

Operating profit
NOK −299,000
Equity
NOK 140.1m
Est. value
NOK 84.5m

Financial health · 2024

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

Who owns OLIMB HOLDING AS?

TEKKAM AS
OLIMB HOLDING AS
· NOK −299,000 profit

OLIMB HOLDING AS has 4 registered shareholders:

All shareholders and roles →

Which companies does OLIMB HOLDING AS own?

OLIMB HOLDING AS holds stakes in 4 companies:

See the full ownership structure →

Group structure

OLIMB HOLDING AS er morselskap for 3 datterselskaper:

Frequently asked questions about OLIMB HOLDING AS

Who owns OLIMB HOLDING AS?

TEKKAM AS is the largest registered owner, with 47.0%.

Who is the general manager of OLIMB HOLDING AS?

Tor Erik Olimb is registered as general manager of OLIMB HOLDING AS.

Where is OLIMB HOLDING AS based?

OLIMB HOLDING AS has its business address in Råde.

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.