BIZTRAC BETA
Other support activities to arts and performing arts

BANGLES & BRASS RECORDS AS

Org. no. 915684602 Limited company (AS) Oslo Incorporated 2015 Active
Ownership graph ↗
Revenue 2025 NOK 4,000
Operating profit NOK −1,000
Equity NOK 148,000
Incorporated 2015
Share capital NOK 39,000

Signals

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

BANGLES & BRASS RECORDS AS is registered as a limited company in Oslo, Oslo with organisation number 915684602. The business is classified under other support activities to arts and performing arts (NACE 90.390). The company was incorporated in 2015. Registered share capital is NOK 39,000, divided into 130 shares. The company's stated purpose is: “Plateselskap, forvalte rettigheter, impresariovirksomhet og andre tjenester som naturlig faller sammen med dette, herunder å delta i andre sels”. The most recent filed accounts, for the 2025 financial year, show NOK 4,000 in revenue and NOK −1,000 in operating profit.

Key figures · 2025

Revenue
NOK 4,000
Operating profit
NOK −1,000
Equity
NOK 148,000
Est. value
NOK 63,000

Financial health · 2025

Liquidity
-21.55
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
104.6%
Very good
Equity as a share of total capital

Who owns BANGLES & BRASS RECORDS AS?

SAHRISH KAPELRUD
BANGLES & BRASS RECORDS AS
NOK 4,000 rev. · NOK −1,000 profit

BANGLES & BRASS RECORDS AS has 13 registered shareholders:

All shareholders and roles →

Frequently asked questions about BANGLES & BRASS RECORDS AS

Who owns BANGLES & BRASS RECORDS AS?

SAHRISH KAPELRUD is the largest registered owner, with 7.7%.

What is the revenue of BANGLES & BRASS RECORDS AS?

BANGLES & BRASS RECORDS AS had revenue of NOK 4,000 in 2025.

Where is BANGLES & BRASS RECORDS AS based?

BANGLES & BRASS 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.