BIZTRAC BETA
Freight transport by road

TROLL BOKS AS

Org. no. 920291198 Limited company (AS) Lillestrøm Incorporated 2017 Active
Ownership graph ↗
Revenue 2024 NOK 850,000
Operating profit NOK 85,000
Equity NOK 93,000
Incorporated 2017
Employees 7
Share capital NOK 30,000

TROLL BOKS AS is registered as a limited company in Lillestrøm, Akershus with organisation number 920291198. The business is classified under freight transport by road (NACE 49.410). The company was incorporated in 2017 and has 7 registered employees. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Salg av tjenester knyttet til transport. Kjøp og salg av bilutstyr og bildeler, dekk og olje. Kjøp og salg deler til motorsykkler, båter og lastebiler og andre kjøretøy. ”. The most recent filed accounts, for the 2024 financial year, show NOK 850,000 in revenue and NOK 85,000 in operating profit.

Key figures · 2024

Revenue
NOK 850,000
Operating profit
NOK 85,000
Equity
NOK 93,000
Est. value
NOK 265,000

Financial health · 2024

Liquidity
1.45
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
8.1%
Weak
Equity as a share of total capital

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

Who owns TROLL BOKS AS?

KRZYSZTOF BEBEN
TROLL BOKS AS
NOK 850,000 rev. · NOK 85,000 profit

TROLL BOKS AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about TROLL BOKS AS

Who owns TROLL BOKS AS?

KRZYSZTOF BEBEN is the largest registered owner, with 100.0%.

What is the revenue of TROLL BOKS AS?

TROLL BOKS AS had revenue of NOK 850,000 in 2024.

Who is the general manager of TROLL BOKS AS?

Krzysztof Beben is registered as general manager of TROLL BOKS AS.

Where is TROLL BOKS AS based?

TROLL BOKS AS has its business address in Skedsmokorset.

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.