BIZTRAC BETA
Other manufacturing n.e.c.

ERLEND MEKKER NICE, AS

Org. no. 931511084 Limited company (AS) Oslo Incorporated 2023 Active
Ownership graph ↗
Revenue 2025 NOK 358,000
Operating profit NOK −85,000
Equity NOK −67,000
Incorporated 2023
Share capital NOK 42,000

Signals

2 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−67k kr).
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−85k kr).

ERLEND MEKKER NICE, AS is registered as a limited company in Oslo, Oslo with organisation number 931511084. The business is classified under other manufacturing n.e.c. (NACE 32.990). The company was incorporated in 2023. Registered share capital is NOK 42,000, divided into 60 shares. The company's stated purpose is: “Pedalbrett til musikere: rådgivning, sammenskruing og salg, og annet som naturlig faller sammen med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 358,000 in revenue and NOK −85,000 in operating profit.

Key figures · 2025

Revenue
NOK 358,000
Operating profit
NOK −85,000
Equity
NOK −67,000

Financial health · 2025

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

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

Who owns ERLEND MEKKER NICE, AS?

ERLEND MARKUSSEN SALTNES
ERLEND MEKKER NICE, AS
NOK 358,000 rev. · NOK −85,000 profit

ERLEND MEKKER NICE, AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about ERLEND MEKKER NICE, AS

Who owns ERLEND MEKKER NICE, AS?

ERLEND MARKUSSEN SALTNES is the largest registered owner, with 90.0%.

What is the revenue of ERLEND MEKKER NICE, AS?

ERLEND MEKKER NICE, AS had revenue of NOK 358,000 in 2025.

Where is ERLEND MEKKER NICE, AS based?

ERLEND MEKKER NICE, 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.