BIZTRAC BETA
COMPANY REGISTER PROFILE
828787942 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 02.09.2026
Motion picture projection activities

DEVA ENTERTAINMENT AS

Org. no. 828787942 Limited company (AS) Oslo Incorporated 2022 Active
Ownership graph ↗
Equity NOK 30,000
Incorporated 2022
Share capital NOK 30,000

DEVA ENTERTAINMENT AS is registered as a limited company in Oslo, Oslo with organisation number 828787942. The business is classified under motion picture projection activities (NACE 59.140). The company was incorporated in 2022. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Underholdning, å leie indiske filmer og framvise i nordiske kinoer.”.

Key figures · 2025

Equity
NOK 30,000
▲ +0 %
Est. value
NOK 54,000

Financial health · 2025

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

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

Who owns DEVA ENTERTAINMENT AS?

No shareholders are registered for DEVA ENTERTAINMENT AS in open Norwegian sources. Shareholder data exists mainly for limited companies (AS/ASA).

Frequently asked questions about DEVA ENTERTAINMENT AS

Who is the general manager of DEVA ENTERTAINMENT AS?

Rahul Vidwat is registered as general manager of DEVA ENTERTAINMENT AS.

Where is DEVA ENTERTAINMENT AS based?

DEVA ENTERTAINMENT AS has its business address in Oslo.

Property

Business address Økernveien 147, 0580 Oslo
Cadastral unit 301-123/5/0/0

28 companies are registered at this address.

The address this company is registered at, from the company register and matched against the cadastre. It does not say who owns the property — a company may be a tenant, and the address is often its accountant's. Source: Brønnøysundregistrene and © Kartverket.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 02.09.2026.

Report a problem

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