BIZTRAC BETA
Site preparation

C3 MASKIN AS

Org. no. 919624310 Limited company (AS) Bærum Incorporated 2017 Active
Ownership graph ↗
Revenue 2024 NOK 17.4m
Operating profit NOK −990,000
Equity NOK −1.8m
Incorporated 2017
Employees 8
Share capital NOK 30,000

Signals

2 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−1,8 mill kr).
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−990k kr).

C3 MASKIN AS is registered as a limited company in Bærum, Akershus with organisation number 919624310. The business is classified under site preparation (NACE 43.120). The company was incorporated in 2017 and has 8 registered employees. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Drift av maskinentreprenørselskap og annet som naturlig faller sammen med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 17.4m in revenue and NOK −990,000 in operating profit.

Key figures · 2024

Revenue
NOK 17.4m
Operating profit
NOK −990,000
Equity
NOK −1.8m

Financial health · 2024

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

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

Who owns C3 MASKIN AS?

C3 HOLDING AS
C3 MASKIN AS
NOK 17.4m rev. · NOK −990,000 profit

C3 MASKIN AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about C3 MASKIN AS

Who owns C3 MASKIN AS?

C3 HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of C3 MASKIN AS?

C3 MASKIN AS had revenue of NOK 17.4m in 2024.

Who is the general manager of C3 MASKIN AS?

Henrik Christian Bræin Sæthre is registered as general manager of C3 MASKIN AS.

Where is C3 MASKIN AS based?

C3 MASKIN AS has its business address in Kolsås.

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.