BIZTRAC BETA
Performing arts activities in music

HONEYBAY MUSIC AS

Org. no. 930482056 Limited company (AS) Oslo Incorporated 2022 Active
Ownership graph ↗
Revenue 2024 NOK 1.6m
Operating profit NOK 181,000
Equity NOK 881,000
Incorporated 2022
Share capital NOK 30,000

HONEYBAY MUSIC AS is registered as a limited company in Oslo, Oslo with organisation number 930482056. The business is classified under performing arts activities in music (NACE 90.201). The company was incorporated in 2022. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Selge tjenester og varer innen sang og kulturformidling, salg og produksjon av musikk, tekst - og annet som naturlig sammenfaller med dette - samt deltakelse i andre selskaper, investeringer og nærliggende virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 1.6m in revenue and NOK 181,000 in operating profit.

Key figures · 2024

Revenue
NOK 1.6m
Operating profit
NOK 181,000
Equity
NOK 881,000
Est. value
NOK 1.3m

Financial health · 2024

Liquidity
2.66
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
62.4%
Very good
Equity as a share of total capital

Who owns HONEYBAY MUSIC AS?

HONEYBAY HOLDING AS
HONEYBAY MUSIC AS
NOK 1.6m rev. · NOK 181,000 profit

HONEYBAY MUSIC AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about HONEYBAY MUSIC AS

Who owns HONEYBAY MUSIC AS?

HONEYBAY HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of HONEYBAY MUSIC AS?

HONEYBAY MUSIC AS had revenue of NOK 1.6m in 2024.

Who is the general manager of HONEYBAY MUSIC AS?

Alexandra Honningsvåg Rotan is registered as general manager of HONEYBAY MUSIC AS.

Where is HONEYBAY MUSIC AS based?

HONEYBAY MUSIC 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.