BIZTRAC BETA
Activities of amusement parks and theme parks

PETER BERGSTRÖMS TIVOLI AS

Org. no. 989323466 Limited company (AS) Indre Østfold Incorporated 2006 Active
Ownership graph ↗
Revenue 2024 NOK 13.6m
Operating profit NOK 1.5m
Equity NOK 2.7m
Incorporated 2006
Employees 12
Share capital NOK 1.0m

PETER BERGSTRÖMS TIVOLI AS is registered as a limited company in Indre Østfold, Østfold with organisation number 989323466. The business is classified under activities of amusement parks and theme parks (NACE 93.210). The company was incorporated in 2006 and has 12 registered employees. Registered share capital is NOK 1.0m, divided into 1000 shares. The company's stated purpose is: “Drift av tivoli, samt kjøp, salg og leie av tivoliutstyr.”. The most recent filed accounts, for the 2024 financial year, show NOK 13.6m in revenue and NOK 1.5m in operating profit.

Key figures · 2024

Revenue
NOK 13.6m
Operating profit
NOK 1.5m
Equity
NOK 2.7m
Est. value
NOK 8.2m

Financial health · 2024

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

Who owns PETER BERGSTRÖMS TIVOLI AS?

PETER BERGSTRM
PETER BERGSTRÖMS TIVOLI AS
NOK 13.6m rev. · NOK 1.5m profit

PETER BERGSTRÖMS TIVOLI AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about PETER BERGSTRÖMS TIVOLI AS

Who owns PETER BERGSTRÖMS TIVOLI AS?

PETER BERGSTRM is the largest registered owner, with 100.0%.

What is the revenue of PETER BERGSTRÖMS TIVOLI AS?

PETER BERGSTRÖMS TIVOLI AS had revenue of NOK 13.6m in 2024.

Who is the general manager of PETER BERGSTRÖMS TIVOLI AS?

Peter Bergström is registered as general manager of PETER BERGSTRÖMS TIVOLI AS.

Where is PETER BERGSTRÖMS TIVOLI AS based?

PETER BERGSTRÖMS TIVOLI AS has its business address in Askim.

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.