biztrac. BETA
COMPANY REGISTER PROFILE
936747353 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Construction of residential and non-residential buildings

GESØ AS

Org. no. 936747353 Limited company (AS) Trondheim Incorporated 2025 Active
Ownership graph ↗
Operating profit NOK −5,000
Equity NOK 11.9m
Incorporated 2025
Share capital NOK 75,000

Signals

2 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−5k kr).
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

GESØ AS is registered as a limited company in Trondheim, Trøndelag with organisation number 936747353. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 2025. Registered share capital is NOK 75,000, divided into 52 shares. The company's stated purpose is: “Selv, eller gjennom hel- eller deleide selskaper, eller ved å samarbeide med andre selskaper, å forestå investeringsvirksomhet, herunder investering i aksjer, obligasjoner, selskapsandeler, fast eiendom, samt annen virksomhet som har naturlig sammenheng med dette.”.

Key figures · 2025

Operating profit
NOK −5,000
Equity
NOK 11.9m
Est. value
NOK 12.2m

Financial health · 2025

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

Who owns GESØ AS?

GESØ AS
· NOK −5,000 profit

GESØ AS has 1 registered shareholder:

All shareholders and roles →

Which companies does GESØ AS own?

GESØ AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about GESØ AS

Who owns GESØ AS?

Geir Søbstad is the largest registered owner, with 100.0%.

Where is GESØ AS based?

GESØ AS has its business address in Trondheim.

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.