BIZTRAC BETA
Buying and selling of own real estate

JON CHRISTENSEN AS

Org. no. 961785200 Limited company (AS) Drammen Incorporated 1991 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −255,000
Equity NOK 17.9m
Incorporated 1991
Share capital NOK 101,000

Signals

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

JON CHRISTENSEN AS is registered as a limited company in Drammen, Buskerud with organisation number 961785200. The business is classified under buying and selling of own real estate (NACE 68.110). The company was incorporated in 1991. Registered share capital is NOK 101,000, divided into 1388 shares. The company's stated purpose is: “Kjøp, salg og drift av eiendommer, samt alt som står i forbindelse med dette, herunder deltagelse i andre selskaper.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −255,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −255,000
Equity
NOK 17.9m
Est. value
NOK 14.1m

Financial health · 2025

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

Who owns JON CHRISTENSEN AS?

JON OLAV REINE CHRISTENSEN
JON CHRISTENSEN AS
NOK 0 rev. · NOK −255,000 profit

JON CHRISTENSEN AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about JON CHRISTENSEN AS

Who owns JON CHRISTENSEN AS?

JON OLAV REINE CHRISTENSEN is the largest registered owner, with 100.0%.

What is the revenue of JON CHRISTENSEN AS?

JON CHRISTENSEN AS had revenue of NOK 0 in 2025.

Who is the general manager of JON CHRISTENSEN AS?

Jon Olav Reine Christensen is registered as general manager of JON CHRISTENSEN AS.

Where is JON CHRISTENSEN AS based?

JON CHRISTENSEN AS has its business address in Drammen.

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.