BIZTRAC BETA
Refrigeration installation, heat pump installation and installation of fireplaces

CR TECH AS

Org. no. 920936687 Limited company (AS) Ullensaker Incorporated 2018 Active
Ownership graph ↗
Revenue 2025 NOK 167,000
Operating profit NOK −16,000
Equity NOK 56,000
Incorporated 2018
Share capital NOK 30,000

Signals

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

CR TECH AS is registered as a limited company in Ullensaker, Akershus with organisation number 920936687. The business is classified under refrigeration installation, heat pump installation and installation of fireplaces (NACE 43.222). The company was incorporated in 2018. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Montering av varmepumper og utleie av bil og verktøy.”. The most recent filed accounts, for the 2025 financial year, show NOK 167,000 in revenue and NOK −16,000 in operating profit.

Key figures · 2025

Revenue
NOK 167,000
Operating profit
NOK −16,000
Equity
NOK 56,000
Est. value
NOK 47,000

Financial health · 2025

Liquidity
5.10
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
39.3%
Weak
Equity as a share of total capital

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

Who owns CR TECH AS?

EMANUEL CROITOR
CR TECH AS
NOK 167,000 rev. · NOK −16,000 profit

CR TECH AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about CR TECH AS

Who owns CR TECH AS?

EMANUEL CROITOR is the largest registered owner, with 55.0%.

What is the revenue of CR TECH AS?

CR TECH AS had revenue of NOK 167,000 in 2025.

Who is the general manager of CR TECH AS?

Emanuel Croitor is registered as general manager of CR TECH AS.

Where is CR TECH AS based?

CR TECH AS has its business address in Gardermoen.

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.