BIZTRAC BETA
Uoppgitt

FUSH HOLDING AS

Org. no. 927729377 Limited company (AS) Frogn Incorporated 2021 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −34,000
Equity NOK 219,000
Incorporated 2021
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−34k kr).

FUSH HOLDING AS is registered as a limited company in Frogn, Akershus with organisation number 927729377. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2021. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Å investere i selskaper og eiendom og alt annet som naturlig faller sammen med dette, herunder å delta i andre selskaper med lignende virksomhet, kjøp og salg av aksjer eller krypto-tokens, eller på annen måte gjøre seg interessert i andre foretagende.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −34,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −34,000
Equity
NOK 219,000
Est. value
NOK 1.2m

Financial health · 2025

Liquidity
49.62
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
53.4%
Very good
Equity as a share of total capital

Who owns FUSH HOLDING AS?

SIGURD FLAATTEN
FUSH HOLDING AS
NOK 0 rev. · NOK −34,000 profit

FUSH HOLDING AS has 2 registered shareholders:

All shareholders and roles →

Which companies does FUSH HOLDING AS own?

FUSH HOLDING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about FUSH HOLDING AS

Who owns FUSH HOLDING AS?

SIGURD FLAATTEN is the largest registered owner, with 50.0%.

What is the revenue of FUSH HOLDING AS?

FUSH HOLDING AS had revenue of NOK 0 in 2025.

Where is FUSH HOLDING AS based?

FUSH HOLDING AS has its business address in Drøbak.

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.