BIZTRAC BETA
Construction of residential and non-residential buildings

SUBSHORE BYGG AS

Org. no. 930461016 Limited company (AS) Stord Incorporated 2022 Active
Ownership graph ↗
Operating profit NOK −6,000
Equity NOK −11,000
Incorporated 2022
Share capital NOK 30,000

Signals

3 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−11k kr).
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−6k kr).
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

SUBSHORE BYGG AS is registered as a limited company in Stord, Vestland with organisation number 930461016. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 2022. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Levering av varer og tjenester innen oppføring og rehabilitering av fast eiendom, samt virksomhet som naturlig står i forbindelse med dette.”.

Key figures · 2025

Operating profit
NOK −6,000
Equity
NOK −11,000

Financial health · 2025

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

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

Who owns SUBSHORE BYGG AS?

SUBSHORE.NO AS
SUBSHORE BYGG AS
· NOK −6,000 profit

SUBSHORE BYGG AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about SUBSHORE BYGG AS

Who owns SUBSHORE BYGG AS?

SUBSHORE.NO AS is the largest registered owner, with 100.0%.

Who is the general manager of SUBSHORE BYGG AS?

Atle Jonny Wigum is registered as general manager of SUBSHORE BYGG AS.

Where is SUBSHORE BYGG AS based?

SUBSHORE BYGG AS has its business address in Stord.

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.