biztrac. BETA
COMPANY REGISTER PROFILE
980224074 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Other business support service activities n.e.c.

JUST CRUZIN PRODUCTION ANS

Org. no. 980224074 General partnership (ANS) Oslo Incorporated 1998 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK 0
Equity NOK 0
Incorporated 1998

JUST CRUZIN PRODUCTION ANS is registered as a general partnership in Oslo, Oslo with organisation number 980224074. The business is classified under other business support service activities n.e.c. (NACE 82.990). The company was incorporated in 1998. The company's stated purpose is: “Arrangør- og konsulentvirksomhet innenfor områdene PR, reklame, markedsføring og events, og produsere varer og tjenester innenfor disse områdene, herunder i samarbeid med andre aktører.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK 0 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK 0
Equity
NOK 0

Financial health · 2025

Liquidity
–
Not available
Current assets ÷ current liabilities
Profitability
–
Not available
Return on total assets
Solidity
–
Not available
Equity as a share of total capital

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

Who owns JUST CRUZIN PRODUCTION ANS?

No shareholders are registered for JUST CRUZIN PRODUCTION ANS in open Norwegian sources. Shareholder data exists mainly for limited companies (AS/ASA).

Frequently asked questions about JUST CRUZIN PRODUCTION ANS

What is the revenue of JUST CRUZIN PRODUCTION ANS?

JUST CRUZIN PRODUCTION ANS had revenue of NOK 0 in 2025.

Who is the general manager of JUST CRUZIN PRODUCTION ANS?

Øystein Lasse Tynning is registered as general manager of JUST CRUZIN PRODUCTION ANS.

Where is JUST CRUZIN PRODUCTION ANS based?

JUST CRUZIN PRODUCTION ANS 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.