BIZTRAC BETA
Motion picture, video and television programme production activities

FRIKSJON FILM AS

Org. no. 919359676 Limited company (AS) Oslo Incorporated 2017 Active
Ownership graph ↗
Revenue 2024 NOK 2.2m
Operating profit NOK −254,000
Equity NOK 158,000
Incorporated 2017
Share capital NOK 45,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−254k kr).

FRIKSJON FILM AS is registered as a limited company in Oslo, Oslo with organisation number 919359676. The business is classified under motion picture, video and television programme production activities (NACE 59.110). The company was incorporated in 2017. Registered share capital is NOK 45,000, divided into 45 shares. The company's stated purpose is: “Produksjon av film, video og fjernsynsprogrammer og annet som naturlig faller sammen med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 2.2m in revenue and NOK −254,000 in operating profit.

Key figures · 2024

Revenue
NOK 2.2m
Operating profit
NOK −254,000
Equity
NOK 158,000
Est. value
NOK 3.8m

Financial health · 2024

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

Who owns FRIKSJON FILM AS?

BILLIE AS
FRIKSJON FILM AS
NOK 2.2m rev. · NOK −254,000 profit

FRIKSJON FILM AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about FRIKSJON FILM AS

Who owns FRIKSJON FILM AS?

BILLIE AS is the largest registered owner, with 33.3%.

What is the revenue of FRIKSJON FILM AS?

FRIKSJON FILM AS had revenue of NOK 2.2m in 2024.

Who is the general manager of FRIKSJON FILM AS?

Yrjan Diogo Sundfør Rodrigues is registered as general manager of FRIKSJON FILM AS.

Where is FRIKSJON FILM AS based?

FRIKSJON FILM 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.