BIZTRAC BETA
Buying and selling of own real estate

ROMERIKE SENTRUM AS

Org. no. 963898169 Limited company (AS) Ullensaker Incorporated 1992 Active
Ownership graph ↗
Revenue 2025 NOK 5.2m
Operating profit NOK 4.5m
Equity NOK 30.5m
Incorporated 1992
Share capital NOK 9.7m

ROMERIKE SENTRUM AS is registered as a limited company in Ullensaker, Akershus with organisation number 963898169. The business is classified under buying and selling of own real estate (NACE 68.110). The company was incorporated in 1992. Registered share capital is NOK 9.7m, divided into 13356 shares. The company's stated purpose is: “Kjøp, salg og utvikling av fast eiendom og alt som står i forbindelse med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 5.2m in revenue and NOK 4.5m in operating profit.

Key figures · 2025

Revenue
NOK 5.2m
Operating profit
NOK 4.5m
Equity
NOK 30.5m
Est. value
NOK 31.1m

Financial health · 2025

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

Who owns ROMERIKE SENTRUM AS?

PATECO AS
ROMERIKE SENTRUM AS
NOK 5.2m rev. · NOK 4.5m profit

ROMERIKE SENTRUM AS has 3 registered shareholders:

All shareholders and roles →

Which companies does ROMERIKE SENTRUM AS own?

ROMERIKE SENTRUM AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about ROMERIKE SENTRUM AS

Who owns ROMERIKE SENTRUM AS?

PATECO AS is the largest registered owner, with 90.4%.

What is the revenue of ROMERIKE SENTRUM AS?

ROMERIKE SENTRUM AS had revenue of NOK 5.2m in 2025.

Who is the general manager of ROMERIKE SENTRUM AS?

Kjell Tømmerås is registered as general manager of ROMERIKE SENTRUM AS.

Where is ROMERIKE SENTRUM AS based?

ROMERIKE SENTRUM AS has its business address in Jessheim.

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.