biztrac. BETA
COMPANY REGISTER PROFILE
999224199 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Arts creation activities in literature

VJ PRODUCTION AS

Org. no. 999224199 Limited company (AS) Oslo Incorporated 2012 Active
Revenue 2025 NOK 0
Operating profit NOK −7,000
Equity NOK 102,000
Incorporated 2012
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−7k kr).

VJ PRODUCTION AS is registered as a limited company in Oslo, Oslo with organisation number 999224199. The business is classified under arts creation activities in literature (NACE 90.111). The company was incorporated in 2012. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Programleder- og journalistvirksomhet samt yte tjenester innen trening.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −7,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −7,000
▼ −19 %
Equity
NOK 102,000
▼ −7 %
Est. value
NOK 127,000

Financial health · 2025

Liquidity
11286.11
Very good
Current assets ÷ current liabilities
Profitability
-7.0%
Not satisfactory
Return on total assets
Solidity
100.0%
Very good
Equity as a share of total capital

Who owns VJ PRODUCTION AS?

VJ PRODUCTION AS
NOK 0 rev. · NOK −7,000 profit

VJ PRODUCTION AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about VJ PRODUCTION AS

Who owns VJ PRODUCTION AS?

Johanna Grønneberg Mesa is the largest registered owner, with 100.0%.

What is the revenue of VJ PRODUCTION AS?

VJ PRODUCTION AS had revenue of NOK 0 in 2025.

Who is the general manager of VJ PRODUCTION AS?

Johanna Grønneberg Mesa is registered as general manager of VJ PRODUCTION AS.

Where is VJ PRODUCTION AS based?

VJ PRODUCTION 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.