BIZTRAC BETA
Rental and operating of own or leased real estate

RINGEBU SENTRUM EIENDOM AS

Org. no. 913023579 Limited company (AS) Gjøvik Incorporated 2013 Active
Ownership graph ↗
Revenue 2024 NOK 4.8m
Operating profit NOK 617,000
Equity NOK 9.1m
Incorporated 2013
Share capital NOK 161,000

Signals

1 flags
  • Nylig endring 2026-02-14 Aksjekapital registrert 2026-02-14.

RINGEBU SENTRUM EIENDOM AS is registered as a limited company in Gjøvik, Innlandet with organisation number 913023579. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2013. Registered share capital is NOK 161,000, divided into 3150 shares. The company's stated purpose is: “Å kjøpe, eie og leie ut fast eiendom, samt hva hermed står i forbindelse, herunder å delta i andre selskaper med lignende virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 4.8m in revenue and NOK 617,000 in operating profit.

Key figures · 2024

Revenue
NOK 4.8m
Operating profit
NOK 617,000
Equity
NOK 9.1m
Est. value
NOK 7.3m

Financial health · 2024

Liquidity
0.28
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
28.1%
Good
Equity as a share of total capital

Who owns RINGEBU SENTRUM EIENDOM AS?

MIRAMARE CAPITAL AS
RINGEBU SENTRUM EIENDOM AS
NOK 4.8m rev. · NOK 617,000 profit

RINGEBU SENTRUM EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about RINGEBU SENTRUM EIENDOM AS

Who owns RINGEBU SENTRUM EIENDOM AS?

MIRAMARE CAPITAL AS is the largest registered owner, with 100.0%.

What is the revenue of RINGEBU SENTRUM EIENDOM AS?

RINGEBU SENTRUM EIENDOM AS had revenue of NOK 4.8m in 2024.

Where is RINGEBU SENTRUM EIENDOM AS based?

RINGEBU SENTRUM EIENDOM AS has its business address in Biri.

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.