BIZTRAC BETA
All other professional, scientific and technical activities n.e.c.

SEVENTEEN AS

Org. no. 817443672 Limited company (AS) Oslo Incorporated 2016 Active
Ownership graph ↗
Revenue 2025 NOK 120,000
Operating profit NOK 96
Equity NOK −298,000
Incorporated 2016
Share capital NOK 30,000

Signals

1 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−298k kr).

SEVENTEEN AS is registered as a limited company in Oslo, Oslo with organisation number 817443672. The business is classified under all other professional, scientific and technical activities n.e.c. (NACE 74.990). The company was incorporated in 2016. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Administrasjon av konsertvirksomhet, booking, salg av musikk og rettighetsforvaltning innen kunst og kultur.”. The most recent filed accounts, for the 2025 financial year, show NOK 120,000 in revenue and NOK 96 in operating profit.

Key figures · 2025

Revenue
NOK 120,000
Operating profit
NOK 96
Equity
NOK −298,000
Est. value
NOK 599

Financial health · 2025

Liquidity
1.99
Good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-280.3%
Weak
Equity as a share of total capital

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

Who owns SEVENTEEN AS?

UNA HEGGESET SAND
SEVENTEEN AS
NOK 120,000 rev. · NOK 96 profit

SEVENTEEN AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about SEVENTEEN AS

Who owns SEVENTEEN AS?

UNA HEGGESET SAND is the largest registered owner, with 100.0%.

What is the revenue of SEVENTEEN AS?

SEVENTEEN AS had revenue of NOK 120,000 in 2025.

Who is the general manager of SEVENTEEN AS?

Erik Sand is registered as general manager of SEVENTEEN AS.

Where is SEVENTEEN AS based?

SEVENTEEN 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.