BIZTRAC BETA
Uoppgitt

FLYVEFISKEN HOLDING AS

Org. no. 933673901 Limited company (AS) Oslo Incorporated 2024 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −93,000
Equity NOK 12.6m
Incorporated 2024
Share capital NOK 36,000

Signals

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

FLYVEFISKEN HOLDING AS is registered as a limited company in Oslo, Oslo with organisation number 933673901. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2024. Registered share capital is NOK 36,000, divided into 36000 shares. The company's stated purpose is: “Kjøp og salg av aksjer og verdipapirer eller på annen måte gjøre seg interessert i andre foretak. Selskapet kan også drive med kjøp/drift av fast eiendom.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −93,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −93,000
Equity
NOK 12.6m
Est. value
NOK 15.6m

Financial health · 2024

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

Who owns FLYVEFISKEN HOLDING AS?

AXEL BORCHGREVINK
FLYVEFISKEN HOLDING AS
NOK 0 rev. · NOK −93,000 profit

FLYVEFISKEN HOLDING AS has 2 registered shareholders:

All shareholders and roles →

Which companies does FLYVEFISKEN HOLDING AS own?

FLYVEFISKEN HOLDING AS holds stakes in 3 companies:

See the full ownership structure →

Frequently asked questions about FLYVEFISKEN HOLDING AS

Who owns FLYVEFISKEN HOLDING AS?

AXEL BORCHGREVINK is the largest registered owner, with 75.0%.

What is the revenue of FLYVEFISKEN HOLDING AS?

FLYVEFISKEN HOLDING AS had revenue of NOK 0 in 2024.

Where is FLYVEFISKEN HOLDING AS based?

FLYVEFISKEN HOLDING AS has its business address in Oslo.

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.