BIZTRAC BETA
Motion picture, video and television programme production activities

VÅRE HISTORIER AS

Org. no. 927019809 Limited company (AS) Senja Incorporated 2021 Active
Ownership graph ↗
Revenue 2025 NOK 2.6m
Operating profit NOK 21,000
Equity NOK 56,000
Incorporated 2021
Share capital NOK 30,000

VÅRE HISTORIER AS is registered as a limited company in Senja, Troms with organisation number 927019809. The business is classified under motion picture, video and television programme production activities (NACE 59.110). The company was incorporated in 2021. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Produksjon og utvikling av film, tv, teater og andre former for historiefortelling og underholdning.”. The most recent filed accounts, for the 2025 financial year, show NOK 2.6m in revenue and NOK 21,000 in operating profit.

Key figures · 2025

Revenue
NOK 2.6m
Operating profit
NOK 21,000
Equity
NOK 56,000
Est. value
NOK 94,000

Financial health · 2025

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

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

Who owns VÅRE HISTORIER AS?

SINDRE OLAV FREDRIKSEN
VÅRE HISTORIER AS
NOK 2.6m rev. · NOK 21,000 profit

VÅRE HISTORIER AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about VÅRE HISTORIER AS

Who owns VÅRE HISTORIER AS?

SINDRE OLAV FREDRIKSEN is the largest registered owner, with 100.0%.

What is the revenue of VÅRE HISTORIER AS?

VÅRE HISTORIER AS had revenue of NOK 2.6m in 2025.

Who is the general manager of VÅRE HISTORIER AS?

Sindre Olav Fredriksen is registered as general manager of VÅRE HISTORIER AS.

Where is VÅRE HISTORIER AS based?

VÅRE HISTORIER AS has its business address in Gryllefjord.

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.