BIZTRAC BETA
Site preparation

CHRISTER JAKOBSEN AS

Org. no. 929475542 Limited company (AS) Vefsn Incorporated 2022 Active
Ownership graph ↗
Revenue 2025 NOK 168,000
Operating profit NOK −51,000
Equity NOK 92,000
Incorporated 2022
Share capital NOK 150,000

Signals

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

CHRISTER JAKOBSEN AS is registered as a limited company in Vefsn, Nordland with organisation number 929475542. The business is classified under site preparation (NACE 43.120). The company was incorporated in 2022. Registered share capital is NOK 150,000, divided into 1500 shares. The company's stated purpose is: “Maskinentreprenørvirksomhet innen anleggsbransjen.”. The most recent filed accounts, for the 2025 financial year, show NOK 168,000 in revenue and NOK −51,000 in operating profit.

Key figures · 2025

Revenue
NOK 168,000
Operating profit
NOK −51,000
Equity
NOK 92,000
Est. value
NOK 98,000

Financial health · 2025

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

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

Who owns CHRISTER JAKOBSEN AS?

CHRISTER JAKOBSEN
CHRISTER JAKOBSEN AS
NOK 168,000 rev. · NOK −51,000 profit

CHRISTER JAKOBSEN AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about CHRISTER JAKOBSEN AS

Who owns CHRISTER JAKOBSEN AS?

CHRISTER JAKOBSEN is the largest registered owner, with 100.0%.

What is the revenue of CHRISTER JAKOBSEN AS?

CHRISTER JAKOBSEN AS had revenue of NOK 168,000 in 2025.

Who is the general manager of CHRISTER JAKOBSEN AS?

Christer Jakobsen is registered as general manager of CHRISTER JAKOBSEN AS.

Where is CHRISTER JAKOBSEN AS based?

CHRISTER JAKOBSEN AS has its business address in Mosjøen.

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.