BIZTRAC BETA
Rental and operating of own or leased real estate

RINGVE LEGESENTER EIENDOM AS

Org. no. 914823145 Limited company (AS) Trondheim Incorporated 2015 Active
Ownership graph ↗
Revenue 2025 NOK 960,000
Operating profit NOK 714,000
Equity NOK 2.4m
Incorporated 2015
Share capital NOK 100,000

RINGVE LEGESENTER EIENDOM AS is registered as a limited company in Trondheim, Trøndelag with organisation number 914823145. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2015. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Drift og utleie av fast eiendom og annen tilknyttet virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 960,000 in revenue and NOK 714,000 in operating profit.

Key figures · 2025

Revenue
NOK 960,000
Operating profit
NOK 714,000
Equity
NOK 2.4m
Est. value
NOK 3.0m

Financial health · 2025

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

Who owns RINGVE LEGESENTER EIENDOM AS?

MARTHE SOFIA BUTT
RINGVE LEGESENTER EIENDOM AS
NOK 960,000 rev. · NOK 714,000 profit

RINGVE LEGESENTER EIENDOM AS has 4 registered shareholders:

All shareholders and roles →

Frequently asked questions about RINGVE LEGESENTER EIENDOM AS

Who owns RINGVE LEGESENTER EIENDOM AS?

MARTHE SOFIA BUTT is the largest registered owner, with 25.0%.

What is the revenue of RINGVE LEGESENTER EIENDOM AS?

RINGVE LEGESENTER EIENDOM AS had revenue of NOK 960,000 in 2025.

Who is the general manager of RINGVE LEGESENTER EIENDOM AS?

Even Mork is registered as general manager of RINGVE LEGESENTER EIENDOM AS.

Where is RINGVE LEGESENTER EIENDOM AS based?

RINGVE LEGESENTER EIENDOM AS has its business address in Trondheim.

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.