BIZTRAC BETA
Buying and selling of own real estate

FST UTVIKLING AS

Org. no. 915921582 Limited company (AS) Øvre Eiker Incorporated 2015 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −16,000
Equity NOK 544,000
Incorporated 2015
Share capital NOK 500,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−16k kr).

FST UTVIKLING AS is registered as a limited company in Øvre Eiker, Buskerud with organisation number 915921582. The business is classified under buying and selling of own real estate (NACE 68.110). The company was incorporated in 2015. Registered share capital is NOK 500,000, divided into 100 shares. The company's stated purpose is: “Kjøpe, utvikle og selge fast eiendom alene eller i samarbeid med andre parter.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −16,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −16,000
Equity
NOK 544,000
Est. value
NOK 497,000

Financial health · 2024

Liquidity
1.11
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
8.9%
Weak
Equity as a share of total capital

Who owns FST UTVIKLING AS?

FLAGET GRUPPEN AS
FST UTVIKLING AS
NOK 0 rev. · NOK −16,000 profit

FST UTVIKLING AS has 2 registered shareholders:

All shareholders and roles →

Which companies does FST UTVIKLING AS own?

FST UTVIKLING AS holds stakes in 2 companies:

See the full ownership structure →

Group structure

FST UTVIKLING AS er morselskap for 1 datterselskap:

Frequently asked questions about FST UTVIKLING AS

Who owns FST UTVIKLING AS?

FLAGET GRUPPEN AS is the largest registered owner, with 50.0%.

What is the revenue of FST UTVIKLING AS?

FST UTVIKLING AS had revenue of NOK 0 in 2024.

Where is FST UTVIKLING AS based?

FST UTVIKLING AS has its business address in Hokksund.

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.