BIZTRAC BETA
Non-specialised wholesale trade

JAKRI AS

Org. no. 976546733 Limited company (AS) Drammen Incorporated 1996 Active
Ownership graph ↗
Revenue 2025 NOK 52,000
Operating profit NOK −7,000
Equity NOK 130,000
Incorporated 1996
Share capital NOK 100,000

Signals

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

JAKRI AS is registered as a limited company in Drammen, Buskerud with organisation number 976546733. The business is classified under non-specialised wholesale trade (NACE 46.900). The company was incorporated in 1996. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “a) Vareimport fra utlandet, spesielt håndverksprodukter, sportsutstyr, hårprodukter og gassprodukter. b) Salg av importerte produkter til detaljist og grossist. c) Drive konsulent-tjenester. d) Eie aksjer/andeler i andre selskaper, samt hva hermed står i forbindelse.”. The most recent filed accounts, for the 2025 financial year, show NOK 52,000 in revenue and NOK −7,000 in operating profit.

Key figures · 2025

Revenue
NOK 52,000
Operating profit
NOK −7,000
Equity
NOK 130,000
Est. value
NOK 79,000

Financial health · 2025

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

Who owns JAKRI AS?

JAN CHRISTENSEN
JAKRI AS
NOK 52,000 rev. · NOK −7,000 profit

JAKRI AS has 6 registered shareholders:

All shareholders and roles →

Frequently asked questions about JAKRI AS

Who owns JAKRI AS?

JAN CHRISTENSEN is the largest registered owner, with 95.0%.

What is the revenue of JAKRI AS?

JAKRI AS had revenue of NOK 52,000 in 2025.

Who is the general manager of JAKRI AS?

Jan Christensen is registered as general manager of JAKRI AS.

Where is JAKRI AS based?

JAKRI AS has its business address in Drammen.

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.