BIZTRAC BETA
Wholesale of beverages

FLUDIUM AS

Org. no. 913461835 Limited company (AS) Arendal Incorporated 2014 Active
Ownership graph ↗
Revenue 2024 NOK 19.3m
Operating profit NOK −243,000
Equity NOK −703,000
Incorporated 2014
Share capital NOK 120,000

Signals

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

FLUDIUM AS is registered as a limited company in Arendal, Agder with organisation number 913461835. The business is classified under wholesale of beverages (NACE 46.340). The company was incorporated in 2014. Registered share capital is NOK 120,000, divided into 1200 shares. The company's stated purpose is: “Import, eksport og videresalg av øl, sider, vin og brennevin og alt som har naturlig sammenheng med dette. Selskapet skal også kunne eie aksjer og andre andeler i andre selskaper og innretninger som driver med det samme eller selger øl, vin og brennevin direkte til forbruker.”. The most recent filed accounts, for the 2024 financial year, show NOK 19.3m in revenue and NOK −243,000 in operating profit.

Key figures · 2024

Revenue
NOK 19.3m
Operating profit
NOK −243,000
Equity
NOK −703,000

Financial health · 2024

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

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

Who owns FLUDIUM AS?

TYSST AS
FLUDIUM AS
NOK 19.3m rev. · NOK −243,000 profit

FLUDIUM AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about FLUDIUM AS

Who owns FLUDIUM AS?

TYSST AS is the largest registered owner, with 50.2%.

What is the revenue of FLUDIUM AS?

FLUDIUM AS had revenue of NOK 19.3m in 2024.

Where is FLUDIUM AS based?

FLUDIUM AS has its business address in Arendal.

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.