BIZTRAC BETA
Business and other management consultancy activities

JAMNE AS

Org. no. 943457972 Limited company (AS) Bærum Incorporated 1987 Active
Ownership graph ↗
Revenue 2024 NOK 60,000
Operating profit NOK −393,000
Equity NOK 57.8m
Incorporated 1987
Share capital NOK 107,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−393k kr).

JAMNE AS is registered as a limited company in Bærum, Akershus with organisation number 943457972. The business is classified under business and other management consultancy activities (NACE 70.200). The company was incorporated in 1987. Registered share capital is NOK 107,000, divided into 107000 shares. The company's stated purpose is: “Yte tjenester innen bedriftsutvikling og å delta med eierandeler og investeringer i forretnings- drift generelt.”. The most recent filed accounts, for the 2024 financial year, show NOK 60,000 in revenue and NOK −393,000 in operating profit.

Key figures · 2024

Revenue
NOK 60,000
Operating profit
NOK −393,000
Equity
NOK 57.8m
Est. value
NOK 33.0m

Financial health · 2024

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

Who owns JAMNE AS?

KJERSTI JAMNE
JAMNE AS
NOK 60,000 rev. · NOK −393,000 profit

JAMNE AS has 4 registered shareholders:

All shareholders and roles →

Which companies does JAMNE AS own?

JAMNE AS holds stakes in 6 companies:

See the full ownership structure →

Frequently asked questions about JAMNE AS

Who owns JAMNE AS?

KJERSTI JAMNE is the largest registered owner, with 80.0%.

What is the revenue of JAMNE AS?

JAMNE AS had revenue of NOK 60,000 in 2024.

Who is the general manager of JAMNE AS?

Johannes Jamne is registered as general manager of JAMNE AS.

Where is JAMNE AS based?

JAMNE AS has its business address in Bekkestua.

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.