BIZTRAC BETA
Wholesale of other machinery and equipment

TOFTIN AS

Org. no. 921208286 Limited company (AS) Trondheim Incorporated 2018 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −13,000
Equity NOK 2.6m
Incorporated 2018
Share capital NOK 100,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−13k kr).

TOFTIN AS is registered as a limited company in Trondheim, Trøndelag with organisation number 921208286. The business is classified under wholesale of other machinery and equipment (NACE 46.640). The company was incorporated in 2018. Registered share capital is NOK 100,000, divided into 1000 shares. The company's stated purpose is: “Investering i aksjer og andeler og dertil hørende virksomhet. Herunder å delta i andre selskap med lignende virksomhet, og kjøp og salg av aksjer eller på annen måte gjøre seg interessert i andre foretak.”. 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 2.6m
Est. value
NOK 4.4m

Financial health · 2024

Liquidity
393.46
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
44.4%
Very good
Equity as a share of total capital

Who owns TOFTIN AS?

GEIR HENRY BERNHARD HELMERSEN
TOFTIN AS
NOK 0 rev. · NOK −13,000 profit

TOFTIN AS has 1 registered shareholder:

All shareholders and roles →

Which companies does TOFTIN AS own?

TOFTIN AS holds stakes in 3 companies:

See the full ownership structure →

Frequently asked questions about TOFTIN AS

Who owns TOFTIN AS?

GEIR HENRY BERNHARD HELMERSEN is the largest registered owner, with 100.0%.

What is the revenue of TOFTIN AS?

TOFTIN AS had revenue of NOK 0 in 2024.

Where is TOFTIN AS based?

TOFTIN AS has its business address in Trondheim.

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.