BIZTRAC BETA
Buying and selling of own real estate

ABU ROMERIKE AS

Org. no. 990830568 Limited company (AS) Eidsvoll Incorporated 2006 Active
Ownership graph ↗
Revenue 2025 NOK 2.4m
Operating profit NOK 887,000
Equity NOK 4.5m
Incorporated 2006
Employees 5
Share capital NOK 3.8m

ABU ROMERIKE AS is registered as a limited company in Eidsvoll, Akershus with organisation number 990830568. The business is classified under buying and selling of own real estate (NACE 68.110). The company was incorporated in 2006 and has 5 registered employees. Registered share capital is NOK 3.8m, divided into 7672 shares. The company's stated purpose is: “Kjøp, utvikling av eiendom samt andre former for eiendomsinvesteringer. Selskapet skal også arbeide med hjelpetiltak innenfor helse og omsorg. Dette gjelder alt fra atferdsproblematikk gjennom kommune og stat, til voksne og eldre med egne behov. Samt undervisning og sikkerhet rundt førstehjelp på bedrifter og arrangement.”. The most recent filed accounts, for the 2025 financial year, show NOK 2.4m in revenue and NOK 887,000 in operating profit.

Key figures · 2025

Revenue
NOK 2.4m
Operating profit
NOK 887,000
Equity
NOK 4.5m
Est. value
NOK 5.7m

Financial health · 2025

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

Who owns ABU ROMERIKE AS?

STARBERG HOLDING AS
ABU ROMERIKE AS
NOK 2.4m rev. · NOK 887,000 profit

ABU ROMERIKE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about ABU ROMERIKE AS

Who owns ABU ROMERIKE AS?

STARBERG HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of ABU ROMERIKE AS?

ABU ROMERIKE AS had revenue of NOK 2.4m in 2025.

Where is ABU ROMERIKE AS based?

ABU ROMERIKE AS has its business address in Eidsvoll.

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.