BIZTRAC BETA
Activities of advertising agencies

NORDIC MERCH AS

Org. no. 912327027 Limited company (AS) Frogn Incorporated 2013 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −4,000
Equity NOK 26,000
Incorporated 2013
Share capital NOK 30,000

Signals

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

NORDIC MERCH AS is registered as a limited company in Frogn, Akershus with organisation number 912327027. The business is classified under activities of advertising agencies (NACE 73.110). The company was incorporated in 2013. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Fasilitering og tilrettelegging for produksjon og design av merchandising og andre produkter og tilhørende tjenester som naturlig faller sammen med dette samt å eie fast eiendom, verdipapirer og andre fordringer.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −4,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −4,000
Equity
NOK 26,000
Est. value
NOK 42,000

Financial health · 2024

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

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

Who owns NORDIC MERCH AS?

JØRGEN OUSMAN JAQUESSON SOWE
NORDIC MERCH AS
NOK 0 rev. · NOK −4,000 profit

NORDIC MERCH AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about NORDIC MERCH AS

Who owns NORDIC MERCH AS?

JØRGEN OUSMAN JAQUESSON SOWE is the largest registered owner, with 40.0%.

What is the revenue of NORDIC MERCH AS?

NORDIC MERCH AS had revenue of NOK 0 in 2024.

Where is NORDIC MERCH AS based?

NORDIC MERCH AS has its business address in Drøbak.

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.