BIZTRAC BETA
Sound recording and music publishing activities

BIG DAY RECORDS AS

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

Signals

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

BIG DAY RECORDS AS is registered as a limited company in Oslo, Oslo with organisation number 916683278. The business is classified under sound recording and music publishing activities (NACE 59.200). The company was incorporated in 2016. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Drift av plateselskap, samt annet som naturlig hører inn under dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 57,000 in revenue and NOK 6,000 in operating profit.

Key figures · 2025

Revenue
NOK 57,000
Operating profit
NOK 6,000
Equity
NOK −11,000
Est. value
NOK 49,000

Financial health · 2025

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

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

Who owns BIG DAY RECORDS AS?

ANNGUNN SØRLI
BIG DAY RECORDS AS
NOK 57,000 rev. · NOK 6,000 profit

BIG DAY RECORDS AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about BIG DAY RECORDS AS

Who owns BIG DAY RECORDS AS?

ANNGUNN SØRLI is the largest registered owner, with 60.0%.

What is the revenue of BIG DAY RECORDS AS?

BIG DAY RECORDS AS had revenue of NOK 57,000 in 2025.

Who is the general manager of BIG DAY RECORDS AS?

Endre Bruskeland is registered as general manager of BIG DAY RECORDS AS.

Where is BIG DAY RECORDS AS based?

BIG DAY 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 15.06.2026.

Report a problem

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