BIZTRAC BETA
Retail sale of other food

HAGABRÅTEN AS

Org. no. 931050044 Limited company (AS) Bærum Incorporated 2023 Active
Ownership graph ↗
Revenue 2025 NOK 4,000
Operating profit NOK −3,000
Equity NOK 20,000
Incorporated 2023
Share capital NOK 30,000

Signals

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

HAGABRÅTEN AS is registered as a limited company in Bærum, Akershus with organisation number 931050044. The business is classified under retail sale of other food (NACE 47.270). The company was incorporated in 2023. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Gårdsbutikk med salg av blomster, håndlagde dekorasjoner, gaveartikler, kurs, konsulentarbeid og annet som naturlig faller sammen med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 4,000 in revenue and NOK −3,000 in operating profit.

Key figures · 2025

Revenue
NOK 4,000
Operating profit
NOK −3,000
Equity
NOK 20,000
Est. value
NOK 11,000

Financial health · 2025

Liquidity
-10.12
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
109.2%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns HAGABRÅTEN AS?

KRISTINA ISAKSSON
HAGABRÅTEN AS
NOK 4,000 rev. · NOK −3,000 profit

HAGABRÅTEN AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about HAGABRÅTEN AS

Who owns HAGABRÅTEN AS?

KRISTINA ISAKSSON is the largest registered owner, with 100.0%.

What is the revenue of HAGABRÅTEN AS?

HAGABRÅTEN AS had revenue of NOK 4,000 in 2025.

Who is the general manager of HAGABRÅTEN AS?

Kristina Isaksson is registered as general manager of HAGABRÅTEN AS.

Where is HAGABRÅTEN AS based?

HAGABRÅTEN AS has its business address in Skui.

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.