BIZTRAC BETA
Wholesale of information and communication equipment

TONULL AS

Org. no. 930366862 Limited company (AS) Skien Incorporated 2022 Active
Ownership graph ↗
Revenue 2025 NOK 4.8m
Operating profit NOK −917,000
Equity NOK −2.6m
Incorporated 2022
Share capital NOK 30,000

Signals

2 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−2,6 mill kr).
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−917k kr).

TONULL AS is registered as a limited company in Skien, Telemark with organisation number 930366862. The business is classified under wholesale of information and communication equipment (NACE 46.500). The company was incorporated in 2022. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Kjøp og salg av it-utstyr og tjenester, samt annen virksomhet som står i naturlig tilknytning til dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 4.8m in revenue and NOK −917,000 in operating profit.

Key figures · 2025

Revenue
NOK 4.8m
Operating profit
NOK −917,000
Equity
NOK −2.6m

Financial health · 2025

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

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

Who owns TONULL AS?

LEFSERESS AS
TONULL AS
NOK 4.8m rev. · NOK −917,000 profit

TONULL AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about TONULL AS

Who owns TONULL AS?

LEFSERESS AS is the largest registered owner, with 80.0%.

What is the revenue of TONULL AS?

TONULL AS had revenue of NOK 4.8m in 2025.

Who is the general manager of TONULL AS?

Filip Fossmo Bekkevold is registered as general manager of TONULL AS.

Where is TONULL AS based?

TONULL AS has its business address in Skien.

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.