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

CMO ENGINEERING AS

Org. no. 923709088 Limited company (AS) Fredrikstad Incorporated 2019 Active
Ownership graph ↗
Revenue 2025 NOK 1.4m
Operating profit NOK 561,000
Equity NOK 347,000
Incorporated 2019
Share capital NOK 30,000

CMO ENGINEERING AS is registered as a limited company in Fredrikstad, Østfold with organisation number 923709088. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 2019. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Konsulenttjenester og rådgivning.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.4m in revenue and NOK 561,000 in operating profit.

Former names: MODULBYGG BÅSTAD AS

Key figures · 2025

Revenue
NOK 1.4m
Operating profit
NOK 561,000
▲ +8375 %
Equity
NOK 347,000
▲ +426 %
Est. value
NOK 954,000

Financial health · 2025

Liquidity
0.89
Weak
Current assets ÷ current liabilities
Profitability
106.7%
Very good
Return on total assets
Solidity
35.0%
Good
Equity as a share of total capital

Who owns CMO ENGINEERING AS?

CMO ENGINEERING AS
NOK 1.4m rev. · NOK 561,000 profit

CMO ENGINEERING AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about CMO ENGINEERING AS

Who owns CMO ENGINEERING AS?

CMO INVEST AS is the largest registered owner, with 100.0%.

What is the revenue of CMO ENGINEERING AS?

CMO ENGINEERING AS had revenue of NOK 1.4m in 2025.

Who is the general manager of CMO ENGINEERING AS?

Tor Jarle Kransberg is registered as general manager of CMO ENGINEERING AS.

Where is CMO ENGINEERING AS based?

CMO ENGINEERING AS has its business address in Fredrikstad.

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.