BIZTRAC BETA
Retail sale of motor vehicles

K.O. JAKOBSEN AS

Org. no. 914405491 Limited company (AS) Senja Incorporated 2014 Active
Ownership graph ↗
Revenue 2025 NOK 259,000
Operating profit NOK −83,000
Equity NOK 140,000
Incorporated 2014
Share capital NOK 30,000

Signals

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

K.O. JAKOBSEN AS is registered as a limited company in Senja, Troms with organisation number 914405491. The business is classified under retail sale of motor vehicles (NACE 47.810). The company was incorporated in 2014. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Kjøpe/selge/reparere biler, utleie av utstyr samt snøbrøyting og vedproduksjon, foruten å kunne engasjere seg i andre selskap med lignende virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 259,000 in revenue and NOK −83,000 in operating profit.

Key figures · 2025

Revenue
NOK 259,000
Operating profit
NOK −83,000
Equity
NOK 140,000
Est. value
NOK 104,000

Financial health · 2025

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

Who owns K.O. JAKOBSEN AS?

KARL OTTO JAKOBSEN
K.O. JAKOBSEN AS
NOK 259,000 rev. · NOK −83,000 profit

K.O. JAKOBSEN AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about K.O. JAKOBSEN AS

Who owns K.O. JAKOBSEN AS?

KARL OTTO JAKOBSEN is the largest registered owner, with 100.0%.

What is the revenue of K.O. JAKOBSEN AS?

K.O. JAKOBSEN AS had revenue of NOK 259,000 in 2025.

Who is the general manager of K.O. JAKOBSEN AS?

Karl Otto Jakobsen is registered as general manager of K.O. JAKOBSEN AS.

Where is K.O. JAKOBSEN AS based?

K.O. JAKOBSEN AS has its business address in Rossfjordstraumen.

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.