BIZTRAC BETA
Business and other management consultancy activities

JAN BRÅTHEN AS

Org. no. 976886828 Limited company (AS) Nes Incorporated 1996 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −361,000
Equity NOK 32.0m
Incorporated 1996
Share capital NOK 2.0m

Signals

2 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−361k kr).
  • Nylig endring 2026-04-20 Adresseendring registrert 2026-04-20.

JAN BRÅTHEN AS is registered as a limited company in Nes, Akershus with organisation number 976886828. The business is classified under business and other management consultancy activities (NACE 70.200). The company was incorporated in 1996. Registered share capital is NOK 2.0m, divided into 1873091 shares. The company's stated purpose is: “Forvaltning av aksjer, forretnings- og eiendomsutvikling, samt annen virksomhet som faller naturlig inn under dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −361,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −361,000
Equity
NOK 32.0m
Est. value
NOK 31.7m

Financial health · 2024

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

Who owns JAN BRÅTHEN AS?

JAN BRÅTHEN
JAN BRÅTHEN AS
NOK 0 rev. · NOK −361,000 profit

JAN BRÅTHEN AS has 1 registered shareholder:

All shareholders and roles →

Which companies does JAN BRÅTHEN AS own?

JAN BRÅTHEN AS holds stakes in 10 companies:

See the full ownership structure →

Frequently asked questions about JAN BRÅTHEN AS

Who owns JAN BRÅTHEN AS?

JAN BRÅTHEN is the largest registered owner, with 100.0%.

What is the revenue of JAN BRÅTHEN AS?

JAN BRÅTHEN AS had revenue of NOK 0 in 2024.

Where is JAN BRÅTHEN AS based?

JAN BRÅTHEN AS has its business address in Årnes.

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.