BIZTRAC BETA
Rental and operating of own or leased real estate

SOLLI EIENDOM AS

Org. no. 980865037 Limited company (AS) Våler Incorporated 1999 Active
Ownership graph ↗
Revenue 2025 NOK 359,000
Operating profit NOK 173,000
Equity NOK 4.9m
Incorporated 1999
Share capital NOK 100,000

SOLLI EIENDOM AS is registered as a limited company in Våler, Innlandet with organisation number 980865037. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 1999. Registered share capital is NOK 100,000, divided into 4590 shares. The company's stated purpose is: “Handel, utleievirksomhet av fast eiendom, landbruksdrift innenfor jord- og skogbruk og annen virksomhet i forbindelse med dette. Selskapet kan også delta i andre selskaper med samme eller lignende formål.”. The most recent filed accounts, for the 2025 financial year, show NOK 359,000 in revenue and NOK 173,000 in operating profit.

Key figures · 2025

Revenue
NOK 359,000
Operating profit
NOK 173,000
Equity
NOK 4.9m
Est. value
NOK 3.9m

Financial health · 2025

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

Who owns SOLLI EIENDOM AS?

TERJE URDAHL
SOLLI EIENDOM AS
NOK 359,000 rev. · NOK 173,000 profit

SOLLI EIENDOM AS has 4 registered shareholders:

All shareholders and roles →

Frequently asked questions about SOLLI EIENDOM AS

Who owns SOLLI EIENDOM AS?

TERJE URDAHL is the largest registered owner, with 28.1%.

What is the revenue of SOLLI EIENDOM AS?

SOLLI EIENDOM AS had revenue of NOK 359,000 in 2025.

Who is the general manager of SOLLI EIENDOM AS?

Hilde Rivenes Urdahl is registered as general manager of SOLLI EIENDOM AS.

Where is SOLLI EIENDOM AS based?

SOLLI EIENDOM AS has its business address in Våler I Solør.

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.