BIZTRAC BETA
Restaurant activities

SEASIDE GASTRO AS

Org. no. 928068609 Limited company (AS) Asker Incorporated 2021 Active
Ownership graph ↗
Revenue 2024 NOK 7.2m
Operating profit NOK −1.3m
Equity NOK −3.5m
Incorporated 2021
Employees 10
Share capital NOK 31,000

Signals

2 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−3,5 mill kr).
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−1,3 mill kr).

SEASIDE GASTRO AS is registered as a limited company in Asker, Akershus with organisation number 928068609. The business is classified under restaurant activities (NACE 56.110). The company was incorporated in 2021 and has 10 registered employees. Registered share capital is NOK 31,000, divided into 1000 shares. The company's stated purpose is: “Drift av restaurant.”. The most recent filed accounts, for the 2024 financial year, show NOK 7.2m in revenue and NOK −1.3m in operating profit.

Key figures · 2024

Revenue
NOK 7.2m
Operating profit
NOK −1.3m
Equity
NOK −3.5m

Financial health · 2024

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

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

Who owns SEASIDE GASTRO AS?

RESTO HOLDING AS
SEASIDE GASTRO AS
NOK 7.2m rev. · NOK −1.3m profit

SEASIDE GASTRO AS has 5 registered shareholders:

All shareholders and roles →

Frequently asked questions about SEASIDE GASTRO AS

Who owns SEASIDE GASTRO AS?

RESTO HOLDING AS is the largest registered owner, with 50.0%.

What is the revenue of SEASIDE GASTRO AS?

SEASIDE GASTRO AS had revenue of NOK 7.2m in 2024.

Who is the general manager of SEASIDE GASTRO AS?

Martins Treimanis is registered as general manager of SEASIDE GASTRO AS.

Where is SEASIDE GASTRO AS based?

SEASIDE GASTRO AS has its business address in Vettre.

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.