BIZTRAC BETA
Buying and selling of own real estate

GUNO AS

Org. no. 992867140 Limited company (AS) Trondheim Incorporated 2008 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −34,000
Equity NOK 934,000
Incorporated 2008
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−34k kr).

GUNO AS is registered as a limited company in Trondheim, Trøndelag with organisation number 992867140. The business is classified under buying and selling of own real estate (NACE 68.110). The company was incorporated in 2008. Registered share capital is NOK 30,000, divided into 400 shares. The company's stated purpose is: “Selskapets virksomhet er investering i aksjer, eiendom, kjøp og salg av varer og tjenester, samt deltakelse i annen virksomhet gjennom aksjetegning eller på annen måte.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −34,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −34,000
Equity
NOK 934,000
Est. value
NOK 730,000

Financial health · 2024

Liquidity
0.00
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
37.9%
Good
Equity as a share of total capital

Who owns GUNO AS?

GUNNAR NORDHEIM
GUNO AS
NOK 0 rev. · NOK −34,000 profit

GUNO AS has 1 registered shareholder:

All shareholders and roles →

Which companies does GUNO AS own?

GUNO AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about GUNO AS

Who owns GUNO AS?

GUNNAR NORDHEIM is the largest registered owner, with 100.0%.

What is the revenue of GUNO AS?

GUNO AS had revenue of NOK 0 in 2024.

Who is the general manager of GUNO AS?

Gunnar Nordheim is registered as general manager of GUNO AS.

Where is GUNO AS based?

GUNO AS has its business address in Heimdal.

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.