BIZTRAC BETA
Rental and operating of own or leased real estate

GIBOR AS

Org. no. 994313010 Limited company (AS) Trondheim Incorporated 2009 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −737,000
Equity NOK 13.2m
Incorporated 2009
Share capital NOK 112,000

Signals

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

GIBOR AS is registered as a limited company in Trondheim, Trøndelag with organisation number 994313010. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2009. Registered share capital is NOK 112,000, divided into 33 shares. The company's stated purpose is: “Investeringsvirksomhet og annen virksomhet beslektet med dette, herunder gjennom eierskap i andre aksjeselskaper.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −737,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −737,000
Equity
NOK 13.2m
Est. value
NOK 10.1m

Financial health · 2024

Liquidity
3.93
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
17.8%
Satisfactory
Equity as a share of total capital

Who owns GIBOR AS?

GISLE BORGAR KRIGSVOLL
GIBOR AS
NOK 0 rev. · NOK −737,000 profit

GIBOR AS has 1 registered shareholder:

All shareholders and roles →

Which companies does GIBOR AS own?

GIBOR AS holds stakes in 6 companies:

See the full ownership structure →

Frequently asked questions about GIBOR AS

Who owns GIBOR AS?

GISLE BORGAR KRIGSVOLL is the largest registered owner, with 100.0%.

What is the revenue of GIBOR AS?

GIBOR AS had revenue of NOK 0 in 2024.

Who is the general manager of GIBOR AS?

Gisle Borgar Krigsvoll is registered as general manager of GIBOR AS.

Where is GIBOR AS based?

GIBOR AS has its business address in Flatåsen.

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.