BIZTRAC BETA
Motion picture, video and television programme production activities

PLAY AS

Org. no. 931759817 Limited company (AS) Larvik Incorporated 2023 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −47,000
Equity NOK 48,000
Incorporated 2023
Share capital NOK 30,000

Signals

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

PLAY AS is registered as a limited company in Larvik, Vestfold with organisation number 931759817. The business is classified under motion picture, video and television programme production activities (NACE 59.110). The company was incorporated in 2023. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Selge varer og tjenester innen produksjon av video og annet som naturlig sammenfaller med dette, samt deltakelse i andre selskaper, investeringer og nærliggende virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −47,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −47,000
Equity
NOK 48,000
Est. value
NOK 87,000

Financial health · 2025

Liquidity
10.19
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
90.2%
Weak
Equity as a share of total capital

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

Who owns PLAY AS?

DAVID RONÉN MAYO
PLAY AS
NOK 0 rev. · NOK −47,000 profit

PLAY AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about PLAY AS

Who owns PLAY AS?

DAVID RONÉN MAYO is the largest registered owner, with 50.0%.

What is the revenue of PLAY AS?

PLAY AS had revenue of NOK 0 in 2025.

Who is the general manager of PLAY AS?

Jørgen Klaastad is registered as general manager of PLAY AS.

Where is PLAY AS based?

PLAY AS has its business address in Larvik.

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.