BIZTRAC BETA
Rental and operating of own or leased real estate

MERKANTIL PARTNER AS

Org. no. 979379587 Limited company (AS) Frogn Incorporated 1997 Active
Ownership graph ↗
Revenue 2024 NOK 68,000
Operating profit NOK −198,000
Equity NOK −97,000
Incorporated 1997
Share capital NOK 100,000

Signals

2 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−97k kr).
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−198k kr).

MERKANTIL PARTNER AS is registered as a limited company in Frogn, Akershus with organisation number 979379587. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 1997. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Investering i fast eiendom og verdipapir, samt konsulent virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 68,000 in revenue and NOK −198,000 in operating profit.

Key figures · 2024

Revenue
NOK 68,000
Operating profit
NOK −198,000
Equity
NOK −97,000

Financial health · 2024

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

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

Who owns MERKANTIL PARTNER AS?

VIGDIS STENSRUD
MERKANTIL PARTNER AS
NOK 68,000 rev. · NOK −198,000 profit

MERKANTIL PARTNER AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about MERKANTIL PARTNER AS

Who owns MERKANTIL PARTNER AS?

VIGDIS STENSRUD is the largest registered owner, with 100.0%.

What is the revenue of MERKANTIL PARTNER AS?

MERKANTIL PARTNER AS had revenue of NOK 68,000 in 2024.

Where is MERKANTIL PARTNER AS based?

MERKANTIL PARTNER 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.