BIZTRAC BETA
Retail sale of second-hand goods

HJEMBRUKET AS

Org. no. 933406067 Limited company (AS) Bærum Incorporated 2024 Active
Ownership graph ↗
Revenue 2024 NOK 276,000
Operating profit NOK −59,000
Equity NOK −30,000
Incorporated 2024
Share capital NOK 30,000

Signals

2 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−30k kr).
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−59k kr).

HJEMBRUKET AS is registered as a limited company in Bærum, Akershus with organisation number 933406067. The business is classified under retail sale of second-hand goods (NACE 47.790). The company was incorporated in 2024. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Gjenbruk av møbler og interiør. Nettsalg. Bærekraftig forbrukerkultur. Miljøansvarlig.”. The most recent filed accounts, for the 2024 financial year, show NOK 276,000 in revenue and NOK −59,000 in operating profit.

Key figures · 2024

Revenue
NOK 276,000
Operating profit
NOK −59,000
Equity
NOK −30,000

Financial health · 2024

Liquidity
3.47
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-92.0%
Weak
Equity as a share of total capital

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

Who owns HJEMBRUKET AS?

Karina Meijers
HJEMBRUKET AS
NOK 276,000 rev. · NOK −59,000 profit

HJEMBRUKET AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about HJEMBRUKET AS

Who owns HJEMBRUKET AS?

Karina Meijers is the largest registered owner, with 100.0%.

What is the revenue of HJEMBRUKET AS?

HJEMBRUKET AS had revenue of NOK 276,000 in 2024.

Who is the general manager of HJEMBRUKET AS?

Karina Meijers is registered as general manager of HJEMBRUKET AS.

Where is HJEMBRUKET AS based?

HJEMBRUKET AS has its business address in Eiksmarka.

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.