biztrac. BETA
COMPANY REGISTER PROFILE
979605390 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Motion picture, video and television programme production activities

4 1/2 FILM AS

Org. no. 979605390 Limited company (AS) Oslo Incorporated 1998 Active
Operating profit NOK −51,000
Equity NOK −1.9m
Incorporated 1998
Share capital NOK 2.9m

Signals

1 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−1,9 mill kr).

4 1/2 FILM AS is registered as a limited company in Oslo, Oslo with organisation number 979605390. The business is classified under motion picture, video and television programme production activities (NACE 59.110). The company was incorporated in 1998. Registered share capital is NOK 2.9m, divided into 29000 shares. The company's stated purpose is: “Utvikling, produksjon og investering i spillefilm, reklame film og alt hva herved medfører, samt deltagelse i andre selskaper med samme eller lignende formål.”.

Former names: SPILLEFILMKOMPANIET 4 1/2 AS

Key figures · 2025

Operating profit
NOK −51,000
▼ −231 %
Equity
NOK −1.9m
▼ −14 %

Financial health · 2025

Liquidity
0.65
Weak
Current assets ÷ current liabilities
Profitability
1.2%
Weak
Return on total assets
Solidity
-160.4%
Weak
Equity as a share of total capital

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

Who owns 4 1/2 FILM AS?

4 1/2 FILM AS has 3 registered shareholders:

All shareholders and roles →

Which companies does 4 1/2 FILM AS own?

4 1/2 FILM AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about 4 1/2 FILM AS

Who owns 4 1/2 FILM AS?

SØNDERBERG EIENDOM AS is the largest registered owner, with 49.0%.

Who is the general manager of 4 1/2 FILM AS?

Håvard Gjerstad is registered as general manager of 4 1/2 FILM AS.

Where is 4 1/2 FILM AS based?

4 1/2 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 03.10.2026.

Report a problem

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