BIZTRAC BETA
Motion picture, video and television programme production activities

GNIST FILM AS

Org. no. 915586813 Limited company (AS) Bergen Incorporated 2015 Active
Ownership graph ↗
Revenue 2025 NOK 300,000
Operating profit NOK 178,000
Equity NOK 146,000
Incorporated 2015
Share capital NOK 30,000

GNIST FILM AS is registered as a limited company in Bergen, Vestland with organisation number 915586813. The business is classified under motion picture, video and television programme production activities (NACE 59.110). The company was incorporated in 2015. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Produksjon av video og kursvirksomhet innen film, teater, friluftsliv og annet som naturlig faller sammen med dette. Utleie av fritidshytter og annet som naturlig faller sammen med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 300,000 in revenue and NOK 178,000 in operating profit.

Key figures · 2025

Revenue
NOK 300,000
Operating profit
NOK 178,000
Equity
NOK 146,000
Est. value
NOK 645,000

Financial health · 2025

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

Who owns GNIST FILM AS?

KRISTIN SÆLEN HAMMERÅS
GNIST FILM AS
NOK 300,000 rev. · NOK 178,000 profit

GNIST FILM AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about GNIST FILM AS

Who owns GNIST FILM AS?

KRISTIN SÆLEN HAMMERÅS is the largest registered owner, with 50.0%.

What is the revenue of GNIST FILM AS?

GNIST FILM AS had revenue of NOK 300,000 in 2025.

Who is the general manager of GNIST FILM AS?

Kristin Sælen Hammerås is registered as general manager of GNIST FILM AS.

Where is GNIST FILM AS based?

GNIST FILM AS has its business address in Bergen.

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.