BIZTRAC BETA
Restaurant activities

FOLLOW MERCI AS

Org. no. 936711758 Limited company (AS) Skien Incorporated 2025 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −11,000
Equity NOK 13,000
Incorporated 2025
Share capital NOK 30,000

Signals

3 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−11k kr).
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.
  • Nystiftet selskap Selskapet ble stiftet 2025-11-19.

FOLLOW MERCI AS is registered as a limited company in Skien, Telemark with organisation number 936711758. The business is classified under restaurant activities (NACE 56.110). The company was incorporated in 2025. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Å eie og drive restauranter, samt virksomhet som naturlig står i forbindelse med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −11,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −11,000
Equity
NOK 13,000
Est. value
NOK 17,000

Financial health · 2025

Liquidity
1.73
Good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
42.0%
Weak
Equity as a share of total capital

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

Who owns FOLLOW MERCI AS?

SOLTYS HOLDING AS
FOLLOW MERCI AS
NOK 0 rev. · NOK −11,000 profit

FOLLOW MERCI AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about FOLLOW MERCI AS

Who owns FOLLOW MERCI AS?

SOLTYS HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of FOLLOW MERCI AS?

FOLLOW MERCI AS had revenue of NOK 0 in 2025.

Where is FOLLOW MERCI AS based?

FOLLOW MERCI AS has its business address in Skien.

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.