BIZTRAC BETA
Site preparation

ROMERIKE ANLEGGSSERVICE AS

Org. no. 925148520 Limited company (AS) Nes Incorporated 2020 Active
Ownership graph ↗
Revenue 2025 NOK 3.8m
Operating profit NOK −410,000
Equity NOK −7,000
Incorporated 2020
Share capital NOK 50,000

Signals

2 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−7k kr).
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−410k kr).

ROMERIKE ANLEGGSSERVICE AS is registered as a limited company in Nes, Akershus with organisation number 925148520. The business is classified under site preparation (NACE 43.120). The company was incorporated in 2020. Registered share capital is NOK 50,000, divided into 50000 shares. The company's stated purpose is: “Å drive næring innen anleggsvirksomhet tilknyttet utomhusarbeider, samt det som naturlig står i forbindelse med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 3.8m in revenue and NOK −410,000 in operating profit.

Key figures · 2025

Revenue
NOK 3.8m
Operating profit
NOK −410,000
Equity
NOK −7,000

Financial health · 2025

Liquidity
0.87
Weak
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-1.0%
Weak
Equity as a share of total capital

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

Who owns ROMERIKE ANLEGGSSERVICE AS?

OGB HOLDING AS
ROMERIKE ANLEGGSSERVICE AS
NOK 3.8m rev. · NOK −410,000 profit

ROMERIKE ANLEGGSSERVICE AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about ROMERIKE ANLEGGSSERVICE AS

Who owns ROMERIKE ANLEGGSSERVICE AS?

OGB HOLDING AS is the largest registered owner, with 60.0%.

What is the revenue of ROMERIKE ANLEGGSSERVICE AS?

ROMERIKE ANLEGGSSERVICE AS had revenue of NOK 3.8m in 2025.

Where is ROMERIKE ANLEGGSSERVICE AS based?

ROMERIKE ANLEGGSSERVICE AS has its business address in Årnes.

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.