BIZTRAC BETA
Activities of excursion and event organisers

TEFRE PRODUKSJONER AS

Org. no. 923112731 Limited company (AS) Oslo Incorporated 2019 Active
Ownership graph ↗
Revenue 2025 NOK 1.1m
Operating profit NOK −238,000
Equity NOK 11,000
Incorporated 2019
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−238k kr).

TEFRE PRODUKSJONER AS is registered as a limited company in Oslo, Oslo with organisation number 923112731. The business is classified under activities of excursion and event organisers (NACE 79.121). The company was incorporated in 2019. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Event-, tv- og kulturproduksjon.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.1m in revenue and NOK −238,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.1m
Operating profit
NOK −238,000
Equity
NOK 11,000
Est. value
NOK 683,000

Financial health · 2024

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

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

Who owns TEFRE PRODUKSJONER AS?

MARI TEFRE
TEFRE PRODUKSJONER AS
NOK 1.1m rev. · NOK −238,000 profit

TEFRE PRODUKSJONER AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about TEFRE PRODUKSJONER AS

Who owns TEFRE PRODUKSJONER AS?

MARI TEFRE is the largest registered owner, with 100.0%.

What is the revenue of TEFRE PRODUKSJONER AS?

TEFRE PRODUKSJONER AS had revenue of NOK 1.1m in 2025.

Who is the general manager of TEFRE PRODUKSJONER AS?

Mari Tefre is registered as general manager of TEFRE PRODUKSJONER AS.

Where is TEFRE PRODUKSJONER AS based?

TEFRE PRODUKSJONER 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.