biztrac. BETA
COMPANY REGISTER PROFILE
890693032 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Other support activities to arts and performing arts

MERE RECORDS DA

Org. no. 890693032 General partnership with shared liability (DA) Oslo Incorporated 2006 Active
Revenue 2025 NOK 3,000
Operating profit NOK −9,000
Equity NOK −351,000
Incorporated 2006

Signals

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

MERE RECORDS DA is registered as a general partnership with shared liability in Oslo, Oslo with organisation number 890693032. The business is classified under other support activities to arts and performing arts (NACE 90.390). The company was incorporated in 2006. The company's stated purpose is: “Drive plateselskap: spille inn/produsere/utgi kunstmusikk/lydkunst/visuell kunst i/på egnede formater/medier og drive handel med/produksjon av produkter som naturlig hører sammen med dette, samt i andre virksomheter innenfor samme bransje.”. The most recent filed accounts, for the 2025 financial year, show NOK 3,000 in revenue and NOK −9,000 in operating profit.

Key figures · 2025

Revenue
NOK 3,000
▼ −52 %
Operating profit
NOK −9,000
▼ −28 %
Equity
NOK −351,000
▼ −2 %

Financial health · 2025

Liquidity
0.22
Not satisfactory
Current assets ÷ current liabilities
Profitability
–
Not available
Return on total assets
Solidity
-356.3%
Weak
Equity as a share of total capital

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

Who owns MERE RECORDS DA?

No shareholders are registered for MERE RECORDS DA in open Norwegian sources. Shareholder data exists mainly for limited companies (AS/ASA).

Frequently asked questions about MERE RECORDS DA

What is the revenue of MERE RECORDS DA?

MERE RECORDS DA had revenue of NOK 3,000 in 2025.

Where is MERE RECORDS DA based?

MERE RECORDS DA 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.