biztrac. BETA
COMPANY REGISTER PROFILE
860502712 ORG. NO. 2025 ACCOUNTS 9 SECTIONS
Active UPDATED 03.10.2026
Rental and operating of own or leased real estate

BATJAK AS

Org. no. 860502712 Limited company (AS) Skien Incorporated 1991 Active
Ownership graph ↗
Revenue 2025 NOK 6,000
Operating profit NOK −89,000
Equity NOK 69.1m
Incorporated 1991
Share capital NOK 2.0m

Signals

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

BATJAK AS is registered as a limited company in Skien, Telemark with organisation number 860502712. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 1991. Registered share capital is NOK 2.0m, divided into 2000 shares. The company's stated purpose is: “Investering og forvaltning av fast eiendom, samt hva herved står i forbindelse.”. The most recent filed accounts, for the 2025 financial year, show NOK 6,000 in revenue and NOK −89,000 in operating profit.

Former names: CAND PHARM C CHRISTOFFERSEN TELEMARK FARGE ENGROS AS

Key figures · 2025

Revenue
NOK 6,000
▲ +0 %
Operating profit
NOK −89,000
▲ +41 %
Equity
NOK 69.1m
▲ +1 %
Est. value
NOK 52.0m

Financial health · 2025

Liquidity
10.15
Very good
Current assets ÷ current liabilities
Profitability
5.1%
Weak
Return on total assets
Solidity
96.8%
Very good
Equity as a share of total capital

Who owns BATJAK AS?

BATJAK AS has 2 registered shareholders:

All shareholders and roles →

Which companies does BATJAK AS own?

BATJAK AS holds stakes in 14 companies:

See the full ownership structure →

Frequently asked questions about BATJAK AS

Who owns BATJAK AS?

Morten Christian Christoffersen is the largest registered owner, with 99.9%.

What is the revenue of BATJAK AS?

BATJAK AS had revenue of NOK 6,000 in 2025.

Where is BATJAK AS based?

BATJAK AS has its business address in Skien.

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.