BIZTRAC BETA
Construction of residential and non-residential buildings

SIGITAS BYGG AS

Org. no. 930646571 Limited company (AS) Bømlo Incorporated 2022 Active
Ownership graph ↗
Revenue 2025 NOK 2.8m
Operating profit NOK 29,000
Equity NOK 36,000
Incorporated 2022
Share capital NOK 30,000

SIGITAS BYGG AS is registered as a limited company in Bømlo, Vestland with organisation number 930646571. 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: “Å yte tjenester innen bygge- og anlegg. Oppføring og rehabilitering av bygninger, snekkerarbeid, møbelmontering og alt som følger naturlig av disse bransjene.”. The most recent filed accounts, for the 2025 financial year, show NOK 2.8m in revenue and NOK 29,000 in operating profit.

Key figures · 2025

Revenue
NOK 2.8m
Operating profit
NOK 29,000
Equity
NOK 36,000
Est. value
NOK 100,000

Financial health · 2025

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

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

Who owns SIGITAS BYGG AS?

JUSTAS KYZIKAS
SIGITAS BYGG AS
NOK 2.8m rev. · NOK 29,000 profit

SIGITAS BYGG AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about SIGITAS BYGG AS

Who owns SIGITAS BYGG AS?

JUSTAS KYZIKAS is the largest registered owner, with 100.0%.

What is the revenue of SIGITAS BYGG AS?

SIGITAS BYGG AS had revenue of NOK 2.8m in 2025.

Who is the general manager of SIGITAS BYGG AS?

Justas Kyzikas is registered as general manager of SIGITAS BYGG AS.

Where is SIGITAS BYGG AS based?

SIGITAS BYGG AS has its business address in Foldrøyhamn.

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.