BIZTRAC BETA
Restaurant activities

MERAKI ASKER AS

Org. no. 936187188 Limited company (AS) Asker Incorporated 2025 Active
Ownership graph ↗
Revenue 2025 NOK 1.7m
Operating profit NOK 634,000
Equity NOK 373,000
Incorporated 2025
Employees 7
Share capital NOK 30,000

Signals

1 flags
  • Nystiftet selskap Selskapet ble stiftet 2025-08-26.

MERAKI ASKER AS is registered as a limited company in Asker, Akershus with organisation number 936187188. The business is classified under restaurant activities (NACE 56.110). The company was incorporated in 2025 and has 7 registered employees. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Restaurantvirksomhet og annet som naturlig hører sammen med dette, herunder å delta i andre selskap med lignende virksomhet, og kjøp og salg av aksjer eller på annen måte gjøre seg interessert i andre foretak.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.7m in revenue and NOK 634,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.7m
Operating profit
NOK 634,000
Equity
NOK 373,000
Est. value
NOK 1.9m

Financial health · 2025

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

Who owns MERAKI ASKER AS?

MERAKI AS
MERAKI ASKER AS
NOK 1.7m rev. · NOK 634,000 profit

MERAKI ASKER AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about MERAKI ASKER AS

Who owns MERAKI ASKER AS?

MERAKI AS is the largest registered owner, with 100.0%.

What is the revenue of MERAKI ASKER AS?

MERAKI ASKER AS had revenue of NOK 1.7m in 2025.

Who is the general manager of MERAKI ASKER AS?

Maria Liamaki is registered as general manager of MERAKI ASKER AS.

Where is MERAKI ASKER AS based?

MERAKI ASKER AS has its business address in Asker.

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.