biztrac. BETA
COMPANY REGISTER PROFILE
977515556 ORG. NO. 2025 ACCOUNTS 9 SECTIONS
Active UPDATED 03.10.2026
Performing arts activities in dramatic arts

VIRVEL SCENE AS

Org. no. 977515556 Limited company (AS) Oslo Incorporated 1997 Active
Ownership graph ↗
Revenue 2025 NOK 582,000
Operating profit NOK 69,000
Equity NOK 346,000
Incorporated 1997
Share capital NOK 30,000

VIRVEL SCENE AS is registered as a limited company in Oslo, Oslo with organisation number 977515556. The business is classified under performing arts activities in dramatic arts (NACE 90.202). The company was incorporated in 1997. Registered share capital is NOK 30,000, divided into 60 shares. The company's stated purpose is: “Kunstnerisk produksjon, og alt som står i forbindelse med dette, samt deltagelse i andre selskaper.”. The most recent filed accounts, for the 2025 financial year, show NOK 582,000 in revenue and NOK 69,000 in operating profit.

Former names: TEATERKAMERATENE AS

Key figures · 2025

Revenue
NOK 582,000
▼ −17 %
Operating profit
NOK 69,000
▼ −55 %
Equity
NOK 346,000
▲ +18 %
Est. value
NOK 681,000

Financial health · 2025

Liquidity
8.83
Very good
Current assets ÷ current liabilities
Profitability
19.7%
Very good
Return on total assets
Solidity
91.7%
Very good
Equity as a share of total capital

Who owns VIRVEL SCENE AS?

VIRVEL SCENE AS
NOK 582,000 rev. · NOK 69,000 profit

VIRVEL SCENE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about VIRVEL SCENE AS

Who owns VIRVEL SCENE AS?

Johannes Joner is the largest registered owner, with 100.0%.

What is the revenue of VIRVEL SCENE AS?

VIRVEL SCENE AS had revenue of NOK 582,000 in 2025.

Who is the general manager of VIRVEL SCENE AS?

Johannes Joner is registered as general manager of VIRVEL SCENE AS.

Where is VIRVEL SCENE AS based?

VIRVEL SCENE 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 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.