BIZTRAC BETA
Other real estate activities on a fee or contract basis

RINGEBU BOLIG AS

Org. no. 921277466 Limited company (AS) Larvik Incorporated 2018 Active
Ownership graph ↗
Revenue 2024 NOK 101,000
Operating profit NOK −79,000
Equity NOK 3.4m
Incorporated 2018
Share capital NOK 100,000

Signals

2 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−79k kr).
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

RINGEBU BOLIG AS is registered as a limited company in Larvik, Vestfold with organisation number 921277466. The business is classified under other real estate activities on a fee or contract basis (NACE 68.320). The company was incorporated in 2018. Registered share capital is NOK 100,000, divided into 1000 shares. The company's stated purpose is: “Eie og forvalte tomt beliggende på Ringebu.”. The most recent filed accounts, for the 2024 financial year, show NOK 101,000 in revenue and NOK −79,000 in operating profit.

Key figures · 2024

Revenue
NOK 101,000
Operating profit
NOK −79,000
Equity
NOK 3.4m
Est. value
NOK 2.5m

Financial health · 2025

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

Who owns RINGEBU BOLIG AS?

BERGENE HOLM EIENDOM AS
RINGEBU BOLIG AS
NOK 101,000 rev. · NOK −79,000 profit

RINGEBU BOLIG AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about RINGEBU BOLIG AS

Who owns RINGEBU BOLIG AS?

BERGENE HOLM EIENDOM AS is the largest registered owner, with 100.0%.

What is the revenue of RINGEBU BOLIG AS?

RINGEBU BOLIG AS had revenue of NOK 101,000 in 2024.

Where is RINGEBU BOLIG AS based?

RINGEBU BOLIG AS has its business address in Larvik.

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.