BIZTRAC BETA
Rental and operating of own or leased real estate

SEASIDE INVEST AS

Org. no. 890250912 Limited company (AS) Kristiansund Incorporated 2006 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −10,000
Equity NOK 1.4m
Incorporated 2006
Share capital NOK 139,000

Signals

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

SEASIDE INVEST AS is registered as a limited company in Kristiansund, Møre og Romsdal with organisation number 890250912. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2006. Registered share capital is NOK 139,000, divided into 1385 shares. The company's stated purpose is: “Handelsvirksomhet, konsulentvirksomhet, kjøp og salg av eiendom, investeringsvirksomhet og investering i andre virksomheter.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −10,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −10,000
Equity
NOK 1.4m
Est. value
NOK 963,000

Financial health · 2024

Liquidity
15.59
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
70.1%
Very good
Equity as a share of total capital

Who owns SEASIDE INVEST AS?

STEIN HENDNES
SEASIDE INVEST AS
NOK 0 rev. · NOK −10,000 profit

SEASIDE INVEST AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about SEASIDE INVEST AS

Who owns SEASIDE INVEST AS?

STEIN HENDNES is the largest registered owner, with 100.0%.

What is the revenue of SEASIDE INVEST AS?

SEASIDE INVEST AS had revenue of NOK 0 in 2024.

Who is the general manager of SEASIDE INVEST AS?

Stein Hendnes is registered as general manager of SEASIDE INVEST AS.

Where is SEASIDE INVEST AS based?

SEASIDE INVEST AS has its business address in Kristiansund N.

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.