biztrac. BETA
COMPANY REGISTER PROFILE
986058753 ORG. NO. 2025 ACCOUNTS 9 SECTIONS
Active UPDATED 03.10.2026
Other captive investment companies

FANTUST AS

Org. no. 986058753 Limited company (AS) Oslo Incorporated 2003 Active
Ownership graph ↗
Revenue 2025 NOK 23.6m
Operating profit NOK 5.7m
Equity NOK 74.9m
Incorporated 2003
Share capital NOK 2.5m

FANTUST AS is registered as a limited company in Oslo, Oslo with organisation number 986058753. The business is classified under other captive investment companies (NACE 64.323). The company was incorporated in 2003. Registered share capital is NOK 2.5m, divided into 100 shares. The company's stated purpose is: “Investeringsvirksomhet innen eiendom og verdipapirer samt deltakelse i selskaper med lignende virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 23.6m in revenue and NOK 5.7m in operating profit.

Former names: STARTSKUDDET 475 AS

Key figures · 2025

Revenue
NOK 23.6m
▲ +146 %
Operating profit
NOK 5.7m
▼ −23 %
Equity
NOK 74.9m
▼ −6 %
Est. value
NOK 61.3m

Financial health · 2025

Liquidity
12.89
Very good
Current assets ÷ current liabilities
Profitability
7.2%
Satisfactory
Return on total assets
Solidity
92.8%
Very good
Equity as a share of total capital

Who owns FANTUST AS?

FANTUST AS
NOK 23.6m rev. · NOK 5.7m profit

FANTUST AS has 2 registered shareholders:

All shareholders and roles →

Which companies does FANTUST AS own?

FANTUST AS holds stakes in 21 companies:

See the full ownership structure →

Frequently asked questions about FANTUST AS

Who owns FANTUST AS?

Ingeborg Wiese is the largest registered owner, with 75.0%.

What is the revenue of FANTUST AS?

FANTUST AS had revenue of NOK 23.6m in 2025.

Who is the general manager of FANTUST AS?

Ingeborg Wiese is registered as general manager of FANTUST AS.

Where is FANTUST AS based?

FANTUST 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 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.