BIZTRAC BETA
Computer consultancy and computer facilities management activities

DATABASESENTRALEN AS

Org. no. 998183200 Limited company (AS) Fredrikstad Incorporated 2012 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −21,000
Equity NOK 113,000
Incorporated 2012
Share capital NOK 30,000

Signals

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

DATABASESENTRALEN AS is registered as a limited company in Fredrikstad, Østfold with organisation number 998183200. The business is classified under computer consultancy and computer facilities management activities (NACE 62.200). The company was incorporated in 2012. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Konsulentvirksomhet tilknyttet informasjonsteknologi.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −21,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −21,000
Equity
NOK 113,000
Est. value
NOK 204,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 DATABASESENTRALEN AS?

JON JAHREN
DATABASESENTRALEN AS
NOK 0 rev. · NOK −21,000 profit

DATABASESENTRALEN AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about DATABASESENTRALEN AS

Who owns DATABASESENTRALEN AS?

JON JAHREN is the largest registered owner, with 100.0%.

What is the revenue of DATABASESENTRALEN AS?

DATABASESENTRALEN AS had revenue of NOK 0 in 2025.

Who is the general manager of DATABASESENTRALEN AS?

Jon Jahren is registered as general manager of DATABASESENTRALEN AS.

Where is DATABASESENTRALEN AS based?

DATABASESENTRALEN AS has its business address in Fredrikstad.

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.