BIZTRAC BETA
Motion picture projection activities

FRAM KINO AS

Org. no. 951869880 Limited company (AS) Bodø Incorporated 1989 Active
Ownership graph ↗
Revenue 2024 NOK 15.6m
Operating profit NOK −501,000
Equity NOK 912,000
Incorporated 1989
Employees 15
Share capital NOK 500,000

Signals

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

FRAM KINO AS is registered as a limited company in Bodø, Nordland with organisation number 951869880. The business is classified under motion picture projection activities (NACE 59.140). The company was incorporated in 1989 and has 15 registered employees. Registered share capital is NOK 500,000, divided into 5000 shares. The company's stated purpose is: “Kinodrift, og det som naturlig hører hertil.”. The most recent filed accounts, for the 2024 financial year, show NOK 15.6m in revenue and NOK −501,000 in operating profit.

Key figures · 2024

Revenue
NOK 15.6m
Operating profit
NOK −501,000
Equity
NOK 912,000
Est. value
NOK 26.3m

Financial health · 2024

Liquidity
0.74
Weak
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
16.7%
Satisfactory
Equity as a share of total capital

Who owns FRAM KINO AS?

ERIK JØRGENSEN
FRAM KINO AS
NOK 15.6m rev. · NOK −501,000 profit

FRAM KINO AS has 1 registered shareholder:

All shareholders and roles →

Which companies does FRAM KINO AS own?

FRAM KINO AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about FRAM KINO AS

Who owns FRAM KINO AS?

ERIK JØRGENSEN is the largest registered owner, with 100.0%.

What is the revenue of FRAM KINO AS?

FRAM KINO AS had revenue of NOK 15.6m in 2024.

Who is the general manager of FRAM KINO AS?

Erik Jørgensen is registered as general manager of FRAM KINO AS.

Where is FRAM KINO AS based?

FRAM KINO AS has its business address in Bodø.

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.