biztrac. BETA
COMPANY REGISTER PROFILE
826810262 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Performing arts activities in music

UG RECORDS AS

Org. no. 826810262 Limited company (AS) Oslo Incorporated 2021 Active
Ownership graph ↗
Revenue 2025 NOK 9.0m
Operating profit NOK −749,000
Equity NOK 803,000
Incorporated 2021
Share capital NOK 30,000

Signals

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

UG RECORDS AS is registered as a limited company in Oslo, Oslo with organisation number 826810262. The business is classified under performing arts activities in music (NACE 90.201). The company was incorporated in 2021. Registered share capital is NOK 30,000, divided into 30030 shares. The company's stated purpose is: “Operere innenfor musikkbransjen. Det vil være selskapet til bandet Undergrunn. Det vil ta seg av alt av utgifter og fortjenester som bandet skulle hatt. Dette inkluderer inntekt fra strømmetjenester, lisensavtaler og salg av merchandise.”. The most recent filed accounts, for the 2025 financial year, show NOK 9.0m in revenue and NOK −749,000 in operating profit.

Key figures · 2025

Revenue
NOK 9.0m
▼ −15 %
Operating profit
NOK −749,000
▼ −275 %
Equity
NOK 803,000
▼ −49 %
Est. value
NOK 9.5m

Financial health · 2025

Liquidity
1.10
Satisfactory
Current assets ÷ current liabilities
Profitability
-10.5%
Not satisfactory
Return on total assets
Solidity
10.1%
Satisfactory
Equity as a share of total capital

Who owns UG RECORDS AS?

UG RECORDS AS has 6 registered shareholders:

All shareholders and roles →

Frequently asked questions about UG RECORDS AS

Who owns UG RECORDS AS?

Gabriel Ystad Doria is the largest registered owner, with 16.7%.

What is the revenue of UG RECORDS AS?

UG RECORDS AS had revenue of NOK 9.0m in 2025.

Where is UG RECORDS AS based?

UG RECORDS 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 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.