BIZTRAC BETA
All other professional, scientific and technical activities n.e.c.

ITSSHOWTIME AS

Org. no. 915229468 Limited company (AS) Asker Incorporated 2015 Active
Ownership graph ↗
Revenue 2025 NOK 1.1m
Operating profit NOK 54,000
Equity NOK 56,000
Incorporated 2015
Share capital NOK 30,000

ITSSHOWTIME AS is registered as a limited company in Asker, Akershus with organisation number 915229468. The business is classified under all other professional, scientific and technical activities n.e.c. (NACE 74.990). The company was incorporated in 2015. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Drift av kultur og underholdningstjenester samt utleie av utstyr til slike konsept. Salg av konsulenttjenester og utleie av bobil/campingvogner. Drive leirvirksomhet (Strabasiøs camp) samt utleie av anneks med fellesarealer (kjøkken, bad, vaskerom, gapahuk).”. The most recent filed accounts, for the 2025 financial year, show NOK 1.1m in revenue and NOK 54,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.1m
Operating profit
NOK 54,000
Equity
NOK 56,000
Est. value
NOK 295,000

Financial health · 2025

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

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

Who owns ITSSHOWTIME AS?

TOMMY LINDRUP STEINE
ITSSHOWTIME AS
NOK 1.1m rev. · NOK 54,000 profit

ITSSHOWTIME AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about ITSSHOWTIME AS

Who owns ITSSHOWTIME AS?

TOMMY LINDRUP STEINE is the largest registered owner, with 100.0%.

What is the revenue of ITSSHOWTIME AS?

ITSSHOWTIME AS had revenue of NOK 1.1m in 2025.

Where is ITSSHOWTIME AS based?

ITSSHOWTIME AS has its business address in Sætre.

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.