BIZTRAC BETA
Construction of residential and non-residential buildings

HUG ENTREPRENØR AS

Org. no. 933823814 Limited company (AS) Ålesund Incorporated 2024 Active
Ownership graph ↗
Operating profit NOK 313,000
Equity NOK −9,000
Incorporated 2024
Share capital NOK 100,000

Signals

2 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−9k kr).
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

HUG ENTREPRENØR AS is registered as a limited company in Ålesund, Møre og Romsdal with organisation number 933823814. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 2024. Registered share capital is NOK 100,000, divided into 400000 shares. The company's stated purpose is: “Drive med entreprenørvirksomhet samt at som står i forbindelse med dette og andre produkter/tjenester som naturlig hører sammen med dette herunder å delta i andre selskap med lignende virksomhet, og kjøp og salg av aksjer eller på annen måte gjøre seg interessert i andre foretak.”.

Key figures · 2025

Operating profit
NOK 313,000
Equity
NOK −9,000
Est. value
NOK 1.8m

Financial health · 2025

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

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

Who owns HUG ENTREPRENØR AS?

STORSTUEN INVEST AS
HUG ENTREPRENØR AS
· NOK 313,000 profit

HUG ENTREPRENØR AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about HUG ENTREPRENØR AS

Who owns HUG ENTREPRENØR AS?

STORSTUEN INVEST AS is the largest registered owner, with 100.0%.

Where is HUG ENTREPRENØR AS based?

HUG ENTREPRENØR AS has its business address in Ålesund.

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.