BIZTRAC BETA
Restaurant activities

MIRIN SUSHI AS

Org. no. 934059034 Limited company (AS) Horten Incorporated 2024 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −3,000
Equity NOK 491,000
Incorporated 2024
Employees 8
Share capital NOK 500,000

Signals

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

MIRIN SUSHI AS is registered as a limited company in Horten, Vestfold with organisation number 934059034. The business is classified under restaurant activities (NACE 56.110). The company was incorporated in 2024 and has 8 registered employees. Registered share capital is NOK 500,000, divided into 1000 shares. The company's stated purpose is: “Restaurant- og serveringsvirksomhet, herunder deltakelse i andre selskaper i samme bransje og alt som naturlig hører inn under slik virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −3,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −3,000
Equity
NOK 491,000
Est. value
NOK 651,000

Financial health · 2024

Liquidity
-687.17
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
100.1%
Very good
Equity as a share of total capital

Who owns MIRIN SUSHI AS?

DUY VAN NGUYEN
MIRIN SUSHI AS
NOK 0 rev. · NOK −3,000 profit

MIRIN SUSHI AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about MIRIN SUSHI AS

Who owns MIRIN SUSHI AS?

DUY VAN NGUYEN is the largest registered owner, with 100.0%.

What is the revenue of MIRIN SUSHI AS?

MIRIN SUSHI AS had revenue of NOK 0 in 2024.

Who is the general manager of MIRIN SUSHI AS?

Duy Van Nguyen is registered as general manager of MIRIN SUSHI AS.

Where is MIRIN SUSHI AS based?

MIRIN SUSHI AS has its business address in Horten.

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.