BIZTRAC BETA
Industrial product and fashion design activities

TOKT FILM AS

Org. no. 931175572 Limited company (AS) Ringerike Incorporated 2023 Active
Ownership graph ↗
Revenue 2024 NOK 119,000
Operating profit NOK 31,000
Equity NOK 40,000
Incorporated 2023
Share capital NOK 30,000

TOKT FILM AS is registered as a limited company in Ringerike, Buskerud with organisation number 931175572. The business is classified under industrial product and fashion design activities (NACE 74.110). The company was incorporated in 2023. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Selge tjenester og varer innen film- og videoproduksjon og annet som naturlig sammenfaller med dette, samt deltakelse i andre selskaper, investeringer og nærliggende virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 119,000 in revenue and NOK 31,000 in operating profit.

Key figures · 2024

Revenue
NOK 119,000
Operating profit
NOK 31,000
Equity
NOK 40,000
Est. value
NOK 137,000

Financial health · 2024

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

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

Who owns TOKT FILM AS?

VEBJØRN SEIM BAKKER
TOKT FILM AS
NOK 119,000 rev. · NOK 31,000 profit

TOKT FILM AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about TOKT FILM AS

Who owns TOKT FILM AS?

VEBJØRN SEIM BAKKER is the largest registered owner, with 33.3%.

What is the revenue of TOKT FILM AS?

TOKT FILM AS had revenue of NOK 119,000 in 2024.

Who is the general manager of TOKT FILM AS?

Vebjørn Seim Bakker is registered as general manager of TOKT FILM AS.

Where is TOKT FILM AS based?

TOKT FILM 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.