BIZTRAC BETA
Rental and operating of own or leased real estate

SOGN-EIENDOM AS

Org. no. 914047013 Limited company (AS) Sogndal Incorporated 2014 Active
Ownership graph ↗
Revenue 2025 NOK 4.6m
Operating profit NOK 1.8m
Equity NOK 9.6m
Incorporated 2014
Share capital NOK 3.5m

SOGN-EIENDOM AS is registered as a limited company in Sogndal, Vestland with organisation number 914047013. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2014. Registered share capital is NOK 3.5m, divided into 3493 shares. The company's stated purpose is: “ kjøp, salg og utleie av fast eiendom, utleie av driftsutstyr og andre virksomhetsområder som naturlig faller sammen med dette, herunder å delta i andre selskaper med lignende virksomhet, kjøp og salg av aksjer, eller på annen måte gjøre seg interessert i andre foretak.”. The most recent filed accounts, for the 2025 financial year, show NOK 4.6m in revenue and NOK 1.8m in operating profit.

Key figures · 2025

Revenue
NOK 4.6m
Operating profit
NOK 1.8m
Equity
NOK 9.6m
Est. value
NOK 9.9m

Financial health · 2025

Liquidity
1.23
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
21.1%
Good
Equity as a share of total capital

Who owns SOGN-EIENDOM AS?

GARD THUNE
SOGN-EIENDOM AS
NOK 4.6m rev. · NOK 1.8m profit

SOGN-EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about SOGN-EIENDOM AS

Who owns SOGN-EIENDOM AS?

GARD THUNE is the largest registered owner, with 100.0%.

What is the revenue of SOGN-EIENDOM AS?

SOGN-EIENDOM AS had revenue of NOK 4.6m in 2025.

Who is the general manager of SOGN-EIENDOM AS?

Gard Thune is registered as general manager of SOGN-EIENDOM AS.

Where is SOGN-EIENDOM AS based?

SOGN-EIENDOM AS has its business address in Sogndal.

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.