BIZTRAC BETA
Non-specialised retail sale of predominately food, beverages or tobacco

K.S.H. EIENDOM AS

Org. no. 992047615 Limited company (AS) Sandnes Incorporated 2007 Active
Ownership graph ↗
Revenue 2024 NOK 1.8m
Operating profit NOK 1.4m
Equity NOK 3.3m
Incorporated 2007
Share capital NOK 129,000

K.S.H. EIENDOM AS is registered as a limited company in Sandnes, Rogaland with organisation number 992047615. The business is classified under non-specialised retail sale of predominately food, beverages or tobacco (NACE 47.110). The company was incorporated in 2007. Registered share capital is NOK 129,000, divided into 400 shares. The company's stated purpose is: “Selv, gjennom hel- eller deleide selskaper eller ved samarbeide med andre virksomheter, å forestå kjøp, salg og/eller utleie av fast eiendom, inventar og utstyre, samt tilknyttede virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 1.8m in revenue and NOK 1.4m in operating profit.

Key figures · 2024

Revenue
NOK 1.8m
Operating profit
NOK 1.4m
Equity
NOK 3.3m
Est. value
NOK 6.1m

Financial health · 2024

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

Who owns K.S.H. EIENDOM AS?

KSH INVEST AS
K.S.H. EIENDOM AS
NOK 1.8m rev. · NOK 1.4m profit

K.S.H. EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about K.S.H. EIENDOM AS

Who owns K.S.H. EIENDOM AS?

KSH INVEST AS is the largest registered owner, with 100.0%.

What is the revenue of K.S.H. EIENDOM AS?

K.S.H. EIENDOM AS had revenue of NOK 1.8m in 2024.

Who is the general manager of K.S.H. EIENDOM AS?

Terje Stangeland is registered as general manager of K.S.H. EIENDOM AS.

Where is K.S.H. EIENDOM AS based?

K.S.H. EIENDOM AS has its business address in Sandnes.

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.