BIZTRAC BETA
Motion picture, video and television programme production activities

SEDENDU FILM AS

Org. no. 995998289 Limited company (AS) Oslo Incorporated 2010 Active
Ownership graph ↗
Revenue 2024 NOK 71,000
Operating profit NOK 3,000
Equity NOK 12,000
Incorporated 2010
Share capital NOK 100,000

SEDENDU FILM AS is registered as a limited company in Oslo, Oslo with organisation number 995998289. The business is classified under motion picture, video and television programme production activities (NACE 59.110). The company was incorporated in 2010. Registered share capital is NOK 100,000, divided into 1000 shares. The company's stated purpose is: “Produksjon og salg av film og video. Selskapets formål er å være en viktig og kreativ bidragsyter til norsk film- og videoproduksjon.”. The most recent filed accounts, for the 2024 financial year, show NOK 71,000 in revenue and NOK 3,000 in operating profit.

Key figures · 2024

Revenue
NOK 71,000
Operating profit
NOK 3,000
Equity
NOK 12,000
Est. value
NOK 24,000

Financial health · 2024

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

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

Who owns SEDENDU FILM AS?

GEIR OVE RAMSVIK
SEDENDU FILM AS
NOK 71,000 rev. · NOK 3,000 profit

SEDENDU FILM AS has 4 registered shareholders:

All shareholders and roles →

Frequently asked questions about SEDENDU FILM AS

Who owns SEDENDU FILM AS?

GEIR OVE RAMSVIK is the largest registered owner, with 25.0%.

What is the revenue of SEDENDU FILM AS?

SEDENDU FILM AS had revenue of NOK 71,000 in 2024.

Who is the general manager of SEDENDU FILM AS?

Geir Ove Ramsvik is registered as general manager of SEDENDU FILM AS.

Where is SEDENDU FILM AS based?

SEDENDU 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.