BIZTRAC BETA
Motion picture, video and television programme production activities

BEATE ARNESTAD AS

Org. no. 917737789 Limited company (AS) Oslo Incorporated 2016 Active
Ownership graph ↗
Operating profit NOK −59,000
Equity NOK 1.6m
Incorporated 2016
Share capital NOK 300,000

Signals

2 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−59k kr).
  • Nylig endring 2026-08-04 Aksjekapital registrert 2026-08-04.

BEATE ARNESTAD AS is registered as a limited company in Oslo, Oslo with organisation number 917737789. The business is classified under motion picture, video and television programme production activities (NACE 59.110). The company was incorporated in 2016. Registered share capital is NOK 300,000, divided into 300 shares. The company's stated purpose is: “Filmproduksjon, utleie av arbeidskraft og alt hva hermed er i forbindelse, samt investeringer i eiendom, aksjer og andre verdipapirer og deltakelse i andre foretak.”.

Key figures · 2025

Operating profit
NOK −59,000
Equity
NOK 1.6m
Est. value
NOK 1.3m

Financial health · 2025

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

Who owns BEATE ARNESTAD AS?

BEATE ELISABETH ARNESTAD
BEATE ARNESTAD AS
· NOK −59,000 profit

BEATE ARNESTAD AS has 1 registered shareholder:

All shareholders and roles →

Which companies does BEATE ARNESTAD AS own?

BEATE ARNESTAD AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about BEATE ARNESTAD AS

Who owns BEATE ARNESTAD AS?

BEATE ELISABETH ARNESTAD is the largest registered owner, with 100.0%.

Who is the general manager of BEATE ARNESTAD AS?

Beate Elisabeth Arnestad is registered as general manager of BEATE ARNESTAD AS.

Where is BEATE ARNESTAD AS based?

BEATE ARNESTAD 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 15.06.2026.

Report a problem

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