BIZTRAC BETA
Civil engineering activities

ROMERIKE BOLIGSERVICE AS

Org. no. 933759687 Limited company (AS) Nannestad Incorporated 2024 Active
Ownership graph ↗
Revenue 2025 NOK 190,000
Operating profit NOK 18,000
Equity NOK 38,000
Incorporated 2024
Share capital NOK 30,000

ROMERIKE BOLIGSERVICE AS is registered as a limited company in Nannestad, Akershus with organisation number 933759687. The business is classified under civil engineering activities (NACE 71.121). The company was incorporated in 2024. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Rådgiving, prosjektledelse, salgs og investeringsselskap, herunder delta i andre selskaper med lignende virksomhet, kjøp og salg av aksjer og eiendom eller på annen måte gjøre seg interessert i andre selskaper.”. The most recent filed accounts, for the 2025 financial year, show NOK 190,000 in revenue and NOK 18,000 in operating profit.

Key figures · 2025

Revenue
NOK 190,000
Operating profit
NOK 18,000
Equity
NOK 38,000
Est. value
NOK 111,000

Financial health · 2025

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

Solidity capped at Weak because equity is below NOK 100,000.

Who owns ROMERIKE BOLIGSERVICE AS?

VICKY ASSAD BARKAT
ROMERIKE BOLIGSERVICE AS
NOK 190,000 rev. · NOK 18,000 profit

ROMERIKE BOLIGSERVICE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about ROMERIKE BOLIGSERVICE AS

Who owns ROMERIKE BOLIGSERVICE AS?

VICKY ASSAD BARKAT is the largest registered owner, with 100.0%.

What is the revenue of ROMERIKE BOLIGSERVICE AS?

ROMERIKE BOLIGSERVICE AS had revenue of NOK 190,000 in 2025.

Where is ROMERIKE BOLIGSERVICE AS based?

ROMERIKE BOLIGSERVICE AS has its business address in Nannestad.

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.