biztrac. BETA
COMPANY REGISTER PROFILE
932426978 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Construction of residential and non-residential buildings

JS BYGG HOLDING AS

Org. no. 932426978 Limited company (AS) Stord Incorporated 2023 Active
Operating profit NOK −10,000
Equity NOK 5,000
Incorporated 2023
Share capital NOK 60,000

Signals

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

JS BYGG HOLDING AS is registered as a limited company in Stord, Vestland with organisation number 932426978. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 2023. Registered share capital is NOK 60,000, divided into 1000 shares. The company's stated purpose is: “Investering i aksjer og andre verdipapirer, samt hva hermed står i forbindelse.”.

Key figures · 2025

Operating profit
NOK −10,000
▼ −75 %
Equity
NOK 5,000
▼ −89 %
Est. value
NOK 5,000

Financial health · 2025

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

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

Who owns JS BYGG HOLDING AS?

JS BYGG HOLDING AS
· NOK −10,000 profit

JS BYGG HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does JS BYGG HOLDING AS own?

JS BYGG HOLDING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about JS BYGG HOLDING AS

Who owns JS BYGG HOLDING AS?

Johannes Særsten is the largest registered owner, with 100.0%.

Who is the general manager of JS BYGG HOLDING AS?

Johannes Særsten is registered as general manager of JS BYGG HOLDING AS.

Where is JS BYGG HOLDING AS based?

JS BYGG HOLDING 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 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.