biztrac. BETA
COMPANY REGISTER PROFILE
993452599 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Repair and maintenance of motor vehicles

TE CHRISTIANSEN HOLDING AS

Org. no. 993452599 Limited company (AS) Sarpsborg Incorporated 2008 Active
Ownership graph ↗
Operating profit NOK −39,000
Equity NOK 1.6m
Incorporated 2008
Share capital NOK 100,000

Signals

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

TE CHRISTIANSEN HOLDING AS is registered as a limited company in Sarpsborg, Østfold with organisation number 993452599. The business is classified under repair and maintenance of motor vehicles (NACE 95.310). The company was incorporated in 2008. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Selv, gjennom hel- eller deleide selskaper eller ved samarbeide med andre virksomheter å forestå investeringsvirksomhet, eiendomsforvaltning, forretningsførsel og annen virksomhet beslektet med denne.”.

Key figures · 2025

Operating profit
NOK −39,000
▼ −116 %
Equity
NOK 1.6m
▼ −2 %
Est. value
NOK 1.1m

Financial health · 2025

Liquidity
0.56
Weak
Current assets ÷ current liabilities
Profitability
-1.8%
Not satisfactory
Return on total assets
Solidity
80.6%
Very good
Equity as a share of total capital

Who owns TE CHRISTIANSEN HOLDING AS?

TE CHRISTIANSEN HOLDING AS
· NOK −39,000 profit

TE CHRISTIANSEN HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does TE CHRISTIANSEN HOLDING AS own?

TE CHRISTIANSEN HOLDING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about TE CHRISTIANSEN HOLDING AS

Who owns TE CHRISTIANSEN HOLDING AS?

Truls-Erik Christiansen is the largest registered owner, with 100.0%.

Where is TE CHRISTIANSEN HOLDING AS based?

TE CHRISTIANSEN HOLDING AS has its business address in Borgenhaugen.

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.