BIZTRAC BETA
Rental and operating of own or leased real estate

GBK EIENDOM AS

Org. no. 928038807 Limited company (AS) Trondheim Incorporated 2021 Active
Ownership graph ↗
Revenue 2025 NOK 11.5m
Operating profit NOK 63,000
Equity NOK 105,000
Incorporated 2021
Share capital NOK 30,000

Signals

1 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

GBK EIENDOM AS is registered as a limited company in Trondheim, Trøndelag with organisation number 928038807. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2021. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Investere i og utvikle, selge eller leie ut fast eiendom direkte eller gjennom selskaper.”. The most recent filed accounts, for the 2025 financial year, show NOK 11.5m in revenue and NOK 63,000 in operating profit.

Key figures · 2025

Revenue
NOK 11.5m
Operating profit
NOK 63,000
Equity
NOK 105,000
Est. value
NOK 195,000

Financial health · 2025

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

Who owns GBK EIENDOM AS?

GIBOR AS
GBK EIENDOM AS
NOK 11.5m rev. · NOK 63,000 profit

GBK EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about GBK EIENDOM AS

Who owns GBK EIENDOM AS?

GIBOR AS is the largest registered owner, with 100.0%.

What is the revenue of GBK EIENDOM AS?

GBK EIENDOM AS had revenue of NOK 11.5m in 2025.

Who is the general manager of GBK EIENDOM AS?

Gisle Borgar Krigsvoll is registered as general manager of GBK EIENDOM AS.

Where is GBK EIENDOM AS based?

GBK EIENDOM 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.