BIZTRAC BETA
Other support activities to arts and performing arts

HEFTYE OPPLEVELSER AS

Org. no. 917689490 Limited company (AS) Oslo Incorporated 2016 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −11,000
Equity NOK −11,000
Incorporated 2016
Share capital NOK 30,000

Signals

2 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−11k kr).
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−11k kr).

HEFTYE OPPLEVELSER AS is registered as a limited company in Oslo, Oslo with organisation number 917689490. The business is classified under other support activities to arts and performing arts (NACE 90.390). The company was incorporated in 2016. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Å drive eventvirksomhet og annet som naturlig faller sammen med dette. ”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −11,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −11,000
Equity
NOK −11,000

Financial health · 2025

Liquidity
0.05
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-2598.6%
Weak
Equity as a share of total capital

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

Who owns HEFTYE OPPLEVELSER AS?

ARNE MATHIAS HALVORSEN STRAND
HEFTYE OPPLEVELSER AS
NOK 0 rev. · NOK −11,000 profit

HEFTYE OPPLEVELSER AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about HEFTYE OPPLEVELSER AS

Who owns HEFTYE OPPLEVELSER AS?

ARNE MATHIAS HALVORSEN STRAND is the largest registered owner, with 50.0%.

What is the revenue of HEFTYE OPPLEVELSER AS?

HEFTYE OPPLEVELSER AS had revenue of NOK 0 in 2025.

Where is HEFTYE OPPLEVELSER AS based?

HEFTYE OPPLEVELSER 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.