BIZTRAC BETA
Rental and operating of own or leased real estate

SANDNESVEGEN EIENDOM AS

Org. no. 995482657 Limited company (AS) Eidskog Incorporated 2010 Active
Ownership graph ↗
Revenue 2025 NOK 1.1m
Operating profit NOK 624,000
Equity NOK 2.1m
Incorporated 2010
Share capital NOK 300,000

SANDNESVEGEN EIENDOM AS is registered as a limited company in Eidskog, Innlandet with organisation number 995482657. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2010. Registered share capital is NOK 300,000, divided into 3000 shares. The company's stated purpose is: “Utleie og drift av eiendom, og alt som hermed står i forbindelse. Selskapet kan ha eierinteresser i andre foretak.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.1m in revenue and NOK 624,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.1m
Operating profit
NOK 624,000
Equity
NOK 2.1m
Est. value
NOK 2.8m

Financial health · 2025

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

Who owns SANDNESVEGEN EIENDOM AS?

JAN-KÅRE WILSBERG
SANDNESVEGEN EIENDOM AS
NOK 1.1m rev. · NOK 624,000 profit

SANDNESVEGEN EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about SANDNESVEGEN EIENDOM AS

Who owns SANDNESVEGEN EIENDOM AS?

JAN-KÅRE WILSBERG is the largest registered owner, with 100.0%.

What is the revenue of SANDNESVEGEN EIENDOM AS?

SANDNESVEGEN EIENDOM AS had revenue of NOK 1.1m in 2025.

Who is the general manager of SANDNESVEGEN EIENDOM AS?

Jan-Kåre Wilsberg is registered as general manager of SANDNESVEGEN EIENDOM AS.

Where is SANDNESVEGEN EIENDOM AS based?

SANDNESVEGEN EIENDOM AS has its business address in Matrand.

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.