BIZTRAC BETA
Construction of residential and non-residential buildings

RINGERIKE OPPUSSING AS

Org. no. 827303402 Limited company (AS) Ringerike Incorporated 2021 Active
Ownership graph ↗
Revenue 2025 NOK 2.6m
Operating profit NOK 139,000
Equity NOK 33,000
Incorporated 2021
Share capital NOK 30,000

RINGERIKE OPPUSSING AS is registered as a limited company in Ringerike, Buskerud with organisation number 827303402. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 2021. Registered share capital is NOK 30,000, divided into 3000 shares. The company's stated purpose is: “Oppføring av byggninger.”. The most recent filed accounts, for the 2025 financial year, show NOK 2.6m in revenue and NOK 139,000 in operating profit.

Key figures · 2025

Revenue
NOK 2.6m
Operating profit
NOK 139,000
Equity
NOK 33,000
Est. value
NOK 443,000

Financial health · 2025

Liquidity
1.36
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
6.8%
Weak
Equity as a share of total capital

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

Who owns RINGERIKE OPPUSSING AS?

CORNEL VALER SAMARTINEAN
RINGERIKE OPPUSSING AS
NOK 2.6m rev. · NOK 139,000 profit

RINGERIKE OPPUSSING AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about RINGERIKE OPPUSSING AS

Who owns RINGERIKE OPPUSSING AS?

CORNEL VALER SAMARTINEAN is the largest registered owner, with 100.0%.

What is the revenue of RINGERIKE OPPUSSING AS?

RINGERIKE OPPUSSING AS had revenue of NOK 2.6m in 2025.

Who is the general manager of RINGERIKE OPPUSSING AS?

Cornel Valer Samartinean is registered as general manager of RINGERIKE OPPUSSING AS.

Where is RINGERIKE OPPUSSING AS based?

RINGERIKE OPPUSSING AS has its business address in Hallingby.

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.