BIZTRAC BETA
Construction of residential and non-residential buildings

C3 BYGG AS

Org. no. 834835282 Limited company (AS) Austrheim Incorporated 2025 Active
Ownership graph ↗
Revenue 2025 NOK 982,000
Operating profit NOK 48,000
Equity NOK 63,000
Incorporated 2025
Share capital NOK 30,000

C3 BYGG AS is registered as a limited company in Austrheim, Vestland with organisation number 834835282. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 2025. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Selge varer og tjenester innen oppføring av bygninger og annet som naturlig sammenfaller med dette, samt deltakelse i andre selskaper, investeringer og nærliggende virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 982,000 in revenue and NOK 48,000 in operating profit.

Key figures · 2025

Revenue
NOK 982,000
Operating profit
NOK 48,000
Equity
NOK 63,000
Est. value
NOK 193,000

Financial health · 2025

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

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

Who owns C3 BYGG AS?

SINDRE ALVESTAD SÆTRE
C3 BYGG AS
NOK 982,000 rev. · NOK 48,000 profit

C3 BYGG AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about C3 BYGG AS

Who owns C3 BYGG AS?

SINDRE ALVESTAD SÆTRE is the largest registered owner, with 100.0%.

What is the revenue of C3 BYGG AS?

C3 BYGG AS had revenue of NOK 982,000 in 2025.

Who is the general manager of C3 BYGG AS?

Sindre Alvestad Sætre is registered as general manager of C3 BYGG AS.

Where is C3 BYGG AS based?

C3 BYGG AS has its business address in Austrheim.

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.