BIZTRAC BETA
Uoppgitt

OLJEMARK HOLDING AS

Org. no. 831684232 Limited company (AS) Tønsberg Incorporated 2023 Active
Ownership graph ↗
Operating profit NOK −6,000
Equity NOK −83,000
Incorporated 2023
Share capital NOK 30,000

Signals

2 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−83k kr).
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−6k kr).

OLJEMARK HOLDING AS is registered as a limited company in Tønsberg, Vestfold with organisation number 831684232. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2023. Registered share capital is NOK 30,000, divided into 300000 shares. The company's stated purpose is: “Kjøp og salg av aksjer, investere og eie aksjer og andeler i andre selskap. Vi vil også delta i andre selskaper som naturlig hører inn under dette. Selskapet kan også drive med kjøp/drift av fast eiendom.”.

Key figures · 2025

Operating profit
NOK −6,000
Equity
NOK −83,000

Financial health · 2025

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

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

Who owns OLJEMARK HOLDING AS?

ANDRE OLJEMARK
OLJEMARK HOLDING AS
· NOK −6,000 profit

OLJEMARK HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does OLJEMARK HOLDING AS own?

OLJEMARK HOLDING AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about OLJEMARK HOLDING AS

Who owns OLJEMARK HOLDING AS?

ANDRE OLJEMARK is the largest registered owner, with 100.0%.

Who is the general manager of OLJEMARK HOLDING AS?

Andre Oljemark is registered as general manager of OLJEMARK HOLDING AS.

Where is OLJEMARK HOLDING AS based?

OLJEMARK HOLDING AS has its business address in Tønsberg.

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.