BIZTRAC BETA
Performing arts activities in music

ELVESANG AS

Org. no. 930685313 Limited company (AS) Stange Incorporated 2023 Active
Ownership graph ↗
Revenue 2025 NOK 1.4m
Operating profit NOK −52,000
Equity NOK −12,000
Incorporated 2023
Share capital NOK 30,000

Signals

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

ELVESANG AS is registered as a limited company in Stange, Innlandet with organisation number 930685313. The business is classified under performing arts activities in music (NACE 90.201). The company was incorporated in 2023. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Skal selge varer og tjenester knyttet til Sigurd Holes virksomhet som utøvende musiker og komponist, herunder konserter, musikkinnspillinger (CD, LP og download/streaming), noter, partiturer, komposisjoner og bestillingsverk.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.4m in revenue and NOK −52,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.4m
Operating profit
NOK −52,000
Equity
NOK −12,000

Financial health · 2025

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

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

Who owns ELVESANG AS?

SIGURD HOLE
ELVESANG AS
NOK 1.4m rev. · NOK −52,000 profit

ELVESANG AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about ELVESANG AS

Who owns ELVESANG AS?

SIGURD HOLE is the largest registered owner, with 100.0%.

What is the revenue of ELVESANG AS?

ELVESANG AS had revenue of NOK 1.4m in 2025.

Where is ELVESANG AS based?

ELVESANG AS has its business address in Ottestad.

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.