BIZTRAC BETA
Performing arts activities in dramatic arts

TIGERBUSSEN AS

Org. no. 924702222 Limited company (AS) Oslo Incorporated 2020 Active
Ownership graph ↗
Revenue 2025 NOK 2.0m
Operating profit NOK 326
Equity NOK 55,000
Incorporated 2020
Share capital NOK 30,000

TIGERBUSSEN AS is registered as a limited company in Oslo, Oslo with organisation number 924702222. The business is classified under performing arts activities in dramatic arts (NACE 90.202). The company was incorporated in 2020. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Drifte «Tigerbussen», herunder eierskap, utleie, drift og vedlikehold av denne. «Tigerbussen» er et rullende teater som primært skal benyttes til produksjon og turnévirksomhet av forestillinger rettet mot barn og unge.”. The most recent filed accounts, for the 2025 financial year, show NOK 2.0m in revenue and NOK 326 in operating profit.

Key figures · 2025

Revenue
NOK 2.0m
Operating profit
NOK 326
Equity
NOK 55,000
Est. value
NOK 24,000

Financial health · 2025

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

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

Who owns TIGERBUSSEN AS?

TIGERSTADSTEATRET AS
TIGERBUSSEN AS
NOK 2.0m rev. · NOK 326 profit

TIGERBUSSEN AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about TIGERBUSSEN AS

Who owns TIGERBUSSEN AS?

TIGERSTADSTEATRET AS is the largest registered owner, with 70.0%.

What is the revenue of TIGERBUSSEN AS?

TIGERBUSSEN AS had revenue of NOK 2.0m in 2025.

Who is the general manager of TIGERBUSSEN AS?

Hilde Brinchmann is registered as general manager of TIGERBUSSEN AS.

Where is TIGERBUSSEN AS based?

TIGERBUSSEN AS has its business address in Oslo.

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.