BIZTRAC BETA
Other captive investment companies

FAT HOLDING AS

Org. no. 921818343 Limited company (AS) Ålesund Incorporated 2018 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −13,000
Equity NOK −3,000
Incorporated 2018
Share capital NOK 30,000

Signals

2 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−3k kr).
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−13k kr).

FAT HOLDING AS is registered as a limited company in Ålesund, Møre og Romsdal with organisation number 921818343. The business is classified under other captive investment companies (NACE 64.323). The company was incorporated in 2018. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Eie aksjer i ett eller flere selskaper, og forvalte avkastningen.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −13,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −13,000
Equity
NOK −3,000

Financial health · 2024

Liquidity
0.99
Weak
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-0.2%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns FAT HOLDING AS?

FRANK ALLAN THOMASSEN
FAT HOLDING AS
NOK 0 rev. · NOK −13,000 profit

FAT HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about FAT HOLDING AS

Who owns FAT HOLDING AS?

FRANK ALLAN THOMASSEN is the largest registered owner, with 100.0%.

What is the revenue of FAT HOLDING AS?

FAT HOLDING AS had revenue of NOK 0 in 2024.

Who is the general manager of FAT HOLDING AS?

Frank Allan Thomassen is registered as general manager of FAT HOLDING AS.

Where is FAT HOLDING AS based?

FAT HOLDING AS has its business address in Ellingsøy.

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.