BIZTRAC BETA
Site preparation

FUGAS AS

Org. no. 921366035 Limited company (AS) Tromsø Incorporated 2018 Active
Ownership graph ↗
Revenue 2024 NOK 37.2m
Operating profit NOK 200,000
Equity NOK 446,000
Incorporated 2018
Share capital NOK 30,000

Signals

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

FUGAS AS is registered as a limited company in Tromsø, Troms with organisation number 921366035. The business is classified under site preparation (NACE 43.120). The company was incorporated in 2018. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Maskinentreprenørtjenester som graving av tomter, grøfter og lignende. Samt salg og montering av fundamenteringsløsninger. Selskapet kan delta i andre selskaper med lignende virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 37.2m in revenue and NOK 200,000 in operating profit.

Key figures · 2024

Revenue
NOK 37.2m
Operating profit
NOK 200,000
Equity
NOK 446,000
Est. value
NOK 708,000

Financial health · 2024

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

Who owns FUGAS AS?

HAGFORS HOLDING AS
FUGAS AS
NOK 37.2m rev. · NOK 200,000 profit

FUGAS AS has 1 registered shareholder:

All shareholders and roles →

Group structure

FUGAS AS er morselskap for 1 datterselskap:

Frequently asked questions about FUGAS AS

Who owns FUGAS AS?

HAGFORS HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of FUGAS AS?

FUGAS AS had revenue of NOK 37.2m in 2024.

Who is the general manager of FUGAS AS?

Sture Hagfors is registered as general manager of FUGAS AS.

Where is FUGAS AS based?

FUGAS AS has its business address in Tromsø.

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.