BIZTRAC BETA
Wholesale of other machinery and equipment

JAKO AS

Org. no. 915440053 Limited company (AS) Oslo Incorporated 1949 Active
Ownership graph ↗
Revenue 2024 NOK 116.7m
Operating profit NOK 9.8m
Equity NOK 29.1m
Incorporated 1949
Employees 34
Share capital NOK 870,000

Signals

1 flags
  • Nylig endring 2026-03-03 Adresseendring registrert 2026-03-03.

JAKO AS is registered as a limited company in Oslo, Oslo with organisation number 915440053. The business is classified under wholesale of other machinery and equipment (NACE 46.640). The company was incorporated in 1949 and has 34 registered employees. Registered share capital is NOK 870,000, divided into 1740 shares. The company's stated purpose is: “Handel og agenturvirksomhet, samt deltagelse i annen virksomhet av enhver art.”. The most recent filed accounts, for the 2024 financial year, show NOK 116.7m in revenue and NOK 9.8m in operating profit.

Key figures · 2024

Revenue
NOK 116.7m
Operating profit
NOK 9.8m
Equity
NOK 29.1m
Est. value
NOK 50.2m

Financial health · 2024

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

Who owns JAKO AS?

NOEM HOLDING AS
JAKO AS
NOK 116.7m rev. · NOK 9.8m profit

JAKO AS has 6 registered shareholders:

All shareholders and roles →

Which companies does JAKO AS own?

JAKO AS holds stakes in 2 companies:

See the full ownership structure →

Group structure

JAKO AS er morselskap for 2 datterselskaper:

Frequently asked questions about JAKO AS

Who owns JAKO AS?

NOEM HOLDING AS is the largest registered owner, with 80.1%.

What is the revenue of JAKO AS?

JAKO AS had revenue of NOK 116.7m in 2024.

Who is the general manager of JAKO AS?

Sten Engebretsen is registered as general manager of JAKO AS.

Where is JAKO AS based?

JAKO AS has its business address in Oslo.

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.