BIZTRAC BETA
Motion picture, video and television programme production activities

FILMREDERIET AS

Org. no. 925503525 Limited company (AS) Karmøy Incorporated 2020 Active
Ownership graph ↗
Revenue 2024 NOK 1.1m
Operating profit NOK 127,000
Equity NOK 109,000
Incorporated 2020
Share capital NOK 30,000

Signals

1 flags
  • Nylig endring 2026-07-09 Adresseendring registrert 2026-07-09.

FILMREDERIET AS is registered as a limited company in Karmøy, Rogaland with organisation number 925503525. The business is classified under motion picture, video and television programme production activities (NACE 59.110). The company was incorporated in 2020. Registered share capital is NOK 30,000, divided into 10 shares. The company's stated purpose is: “Arbeide med utvikling av kunstneriske og kommersielle oppdrag innen film og relaterte visuelle medier.”. The most recent filed accounts, for the 2024 financial year, show NOK 1.1m in revenue and NOK 127,000 in operating profit.

Key figures · 2024

Revenue
NOK 1.1m
Operating profit
NOK 127,000
Equity
NOK 109,000
Est. value
NOK 790,000

Financial health · 2024

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

Who owns FILMREDERIET AS?

ODDBJØRN AUSTEVIK
FILMREDERIET AS
NOK 1.1m rev. · NOK 127,000 profit

FILMREDERIET AS has 10 registered shareholders:

All shareholders and roles →

Frequently asked questions about FILMREDERIET AS

Who owns FILMREDERIET AS?

ODDBJØRN AUSTEVIK is the largest registered owner, with 10.0%.

What is the revenue of FILMREDERIET AS?

FILMREDERIET AS had revenue of NOK 1.1m in 2024.

Who is the general manager of FILMREDERIET AS?

Aleksander Nøkling Samsonsen is registered as general manager of FILMREDERIET AS.

Where is FILMREDERIET AS based?

FILMREDERIET AS has its business address in Avaldsnes.

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.