BIZTRAC BETA
Restaurant activities

EIKSMARKA SUSHI AS

Org. no. 918982698 Limited company (AS) Bærum Incorporated 2017 Active
Ownership graph ↗
Revenue 2025 NOK 8.4m
Operating profit NOK −124,000
Equity NOK 700,000
Incorporated 2017
Employees 10
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−124k kr).

EIKSMARKA SUSHI AS is registered as a limited company in Bærum, Akershus with organisation number 918982698. The business is classified under restaurant activities (NACE 56.110). The company was incorporated in 2017 and has 10 registered employees. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Restaurantdrift og salg av take away, samt virksomhet som står i naturlig forbindelse med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 8.4m in revenue and NOK −124,000 in operating profit.

Key figures · 2025

Revenue
NOK 8.4m
Operating profit
NOK −124,000
Equity
NOK 700,000
Est. value
NOK 6.2m

Financial health · 2025

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

Who owns EIKSMARKA SUSHI AS?

RYES AGCAOILI VILLANUEVA
EIKSMARKA SUSHI AS
NOK 8.4m rev. · NOK −124,000 profit

EIKSMARKA SUSHI AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about EIKSMARKA SUSHI AS

Who owns EIKSMARKA SUSHI AS?

RYES AGCAOILI VILLANUEVA is the largest registered owner, with 100.0%.

What is the revenue of EIKSMARKA SUSHI AS?

EIKSMARKA SUSHI AS had revenue of NOK 8.4m in 2025.

Who is the general manager of EIKSMARKA SUSHI AS?

Ryes Agcaoili Villanueva is registered as general manager of EIKSMARKA SUSHI AS.

Where is EIKSMARKA SUSHI AS based?

EIKSMARKA SUSHI AS has its business address in Eiksmarka.

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.