BIZTRAC BETA
COMPANY REGISTER PROFILE
916502869 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 15.06.2026
Civil engineering activities

CHRISTOFFERSEN AS

Org. no. 916502869 Limited company (AS) Tinn Incorporated 2015 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −114,000
Equity NOK 334,000
Incorporated 2015
Share capital NOK 30,000

Signals

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

CHRISTOFFERSEN AS is registered as a limited company in Tinn, Telemark with organisation number 916502869. The business is classified under civil engineering activities (NACE 71.121). The company was incorporated in 2015. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Konsulent og anleggsteknikk.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −114,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −114,000
Equity
NOK 334,000
Est. value
NOK 543,000

Financial health · 2025

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

Who owns CHRISTOFFERSEN AS?

STIAN CHRISTOFFER CHRISTOFFERSEN
CHRISTOFFERSEN AS
NOK 0 rev. · NOK −114,000 profit

CHRISTOFFERSEN AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about CHRISTOFFERSEN AS

Who owns CHRISTOFFERSEN AS?

STIAN CHRISTOFFER CHRISTOFFERSEN is the largest registered owner, with 100.0%.

What is the revenue of CHRISTOFFERSEN AS?

CHRISTOFFERSEN AS had revenue of NOK 0 in 2025.

Who is the general manager of CHRISTOFFERSEN AS?

Stian Christoffer Christoffersen is registered as general manager of CHRISTOFFERSEN AS.

Where is CHRISTOFFERSEN AS based?

CHRISTOFFERSEN AS has its business address in Tinn Austbygd.

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.