biztrac. BETA
COMPANY REGISTER PROFILE
924061316 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Rental and operating of own or leased real estate

S.E.S EIENDOM AS

Org. no. 924061316 Limited company (AS) Kvinnherad Incorporated 2019 Active
Ownership graph ↗
Operating profit NOK −31,000
Equity NOK 25.6m
Incorporated 2019
Share capital NOK 486,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−31k kr).

S.E.S EIENDOM AS is registered as a limited company in Kvinnherad, Vestland with organisation number 924061316. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2019. Registered share capital is NOK 486,000, divided into 1812 shares. The company's stated purpose is: “Investering i, utleie, drift og forvaltning av faste eiendommer. Investering i aksjer og andre verdipapirer samt å yte lån eller garantier for lån. Videre skal selskapet kunne påta seg utredningsarbeid, konsulenttjenester, økonomiske rådgivningstjenester samt hva hermed står i forbindelse.”.

Key figures · 2025

Operating profit
NOK −31,000
▼ −104 %
Equity
NOK 25.6m
▲ +1 %
Est. value
NOK 19.7m

Financial health · 2025

Liquidity
13.29
Very good
Current assets ÷ current liabilities
Profitability
5.1%
Weak
Return on total assets
Solidity
95.5%
Very good
Equity as a share of total capital

Who owns S.E.S EIENDOM AS?

S.E.S EIENDOM AS
· NOK −31,000 profit

S.E.S EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Which companies does S.E.S EIENDOM AS own?

S.E.S EIENDOM AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about S.E.S EIENDOM AS

Who owns S.E.S EIENDOM AS?

Svein Magnus Eide is the largest registered owner, with 100.0%.

Where is S.E.S EIENDOM AS based?

S.E.S EIENDOM AS has its business address in Hatlestrand.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.