BIZTRAC BETA
Buying and selling of own real estate

HJEMOM BERGERLØKKA AS

Org. no. 927002922 Limited company (AS) Asker Incorporated 2021 Active
Ownership graph ↗
Revenue 2025 NOK 7.3m
Operating profit NOK 4.3m
Equity NOK 45.6m
Incorporated 2021
Share capital NOK 8.0m

Signals

1 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

HJEMOM BERGERLØKKA AS is registered as a limited company in Asker, Akershus with organisation number 927002922. The business is classified under buying and selling of own real estate (NACE 68.110). The company was incorporated in 2021. Registered share capital is NOK 8.0m, divided into 80000 shares. The company's stated purpose is: “Kjøp, salg, utvikling og forvaltning av fast eiendom samt annen beslektet virksomhet, herunder å finansiere og eie andeler i selskaper med tilsvarende formål.”. The most recent filed accounts, for the 2025 financial year, show NOK 7.3m in revenue and NOK 4.3m in operating profit.

Key figures · 2025

Revenue
NOK 7.3m
Operating profit
NOK 4.3m
Equity
NOK 45.6m
Est. value
NOK 38.7m

Financial health · 2025

Liquidity
1.51
Good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
36.2%
Good
Equity as a share of total capital

Who owns HJEMOM BERGERLØKKA AS?

GRUNNSTEINEN BOLIGUTLEIE AS
HJEMOM BERGERLØKKA AS
NOK 7.3m rev. · NOK 4.3m profit

HJEMOM BERGERLØKKA AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about HJEMOM BERGERLØKKA AS

Who owns HJEMOM BERGERLØKKA AS?

GRUNNSTEINEN BOLIGUTLEIE AS is the largest registered owner, with 100.0%.

What is the revenue of HJEMOM BERGERLØKKA AS?

HJEMOM BERGERLØKKA AS had revenue of NOK 7.3m in 2025.

Where is HJEMOM BERGERLØKKA AS based?

HJEMOM BERGERLØKKA AS has its business address in Billingstad.

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.