BIZTRAC BETA
Plumbing installation

RINGERIKE BAD OG BYGG AS

Org. no. 918772030 Limited company (AS) Ringerike Incorporated 2017 Active
Ownership graph ↗
Revenue 2024 NOK 1.9m
Operating profit NOK −210,000
Equity NOK 565,000
Incorporated 2017
Share capital NOK 40,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−210k kr).

RINGERIKE BAD OG BYGG AS is registered as a limited company in Ringerike, Buskerud with organisation number 918772030. The business is classified under plumbing installation (NACE 43.221). The company was incorporated in 2017. Registered share capital is NOK 40,000, divided into 40000 shares. The company's stated purpose is: “Bygging og rehabilitering av bad, og andre tjenester som naturlig hører inn under dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 1.9m in revenue and NOK −210,000 in operating profit.

Key figures · 2024

Revenue
NOK 1.9m
Operating profit
NOK −210,000
Equity
NOK 565,000
Est. value
NOK 897,000

Financial health · 2024

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

Who owns RINGERIKE BAD OG BYGG AS?

STIG ERIKSEN
RINGERIKE BAD OG BYGG AS
NOK 1.9m rev. · NOK −210,000 profit

RINGERIKE BAD OG BYGG AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about RINGERIKE BAD OG BYGG AS

Who owns RINGERIKE BAD OG BYGG AS?

STIG ERIKSEN is the largest registered owner, with 100.0%.

What is the revenue of RINGERIKE BAD OG BYGG AS?

RINGERIKE BAD OG BYGG AS had revenue of NOK 1.9m in 2024.

Who is the general manager of RINGERIKE BAD OG BYGG AS?

Stig Eriksen is registered as general manager of RINGERIKE BAD OG BYGG AS.

Where is RINGERIKE BAD OG BYGG AS based?

RINGERIKE BAD OG BYGG AS has its business address in Sokna.

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.