BIZTRAC BETA
Gambling and betting activities

SUPERFLAKS AS

Org. no. 919846534 Limited company (AS) Ringerike Incorporated 2017 Active
Ownership graph ↗
Revenue 2024 NOK 1.8m
Operating profit NOK 293,000
Equity NOK −2.3m
Incorporated 2017
Share capital NOK 1.0m

Signals

2 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−2,3 mill kr).
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

SUPERFLAKS AS is registered as a limited company in Ringerike, Buskerud with organisation number 919846534. The business is classified under gambling and betting activities (NACE 92.000). The company was incorporated in 2017. Registered share capital is NOK 1.0m, divided into 1000 shares. The company's stated purpose is: “Lotteri og totalisatorspill.”. The most recent filed accounts, for the 2024 financial year, show NOK 1.8m in revenue and NOK 293,000 in operating profit.

Key figures · 2024

Revenue
NOK 1.8m
Operating profit
NOK 293,000
Equity
NOK −2.3m
Est. value
NOK 1.6m

Financial health · 2024

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

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

Who owns SUPERFLAKS AS?

HEXAGON AS
SUPERFLAKS AS
NOK 1.8m rev. · NOK 293,000 profit

SUPERFLAKS AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about SUPERFLAKS AS

Who owns SUPERFLAKS AS?

HEXAGON AS is the largest registered owner, with 100.0%.

What is the revenue of SUPERFLAKS AS?

SUPERFLAKS AS had revenue of NOK 1.8m in 2024.

Who is the general manager of SUPERFLAKS AS?

Kenneth Matsson is registered as general manager of SUPERFLAKS AS.

Where is SUPERFLAKS AS based?

SUPERFLAKS AS has its business address in Hønefoss.

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.