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

GBE BYGG AS

Org. no. 927174146 Limited company (AS) Oslo Incorporated 2021 Active
Revenue 2025 NOK 4.8m
Operating profit NOK −505,000
Equity NOK 211,000
Incorporated 2021
Share capital NOK 100,000

Signals

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

GBE BYGG AS is registered as a limited company in Oslo, Oslo with organisation number 927174146. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 2021. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Levere håndverkstjenester innen bygg- og anlegg, samt virksomhet som naturlig faller inn under dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 4.8m in revenue and NOK −505,000 in operating profit.

Key figures · 2025

Revenue
NOK 4.8m
▼ −49 %
Operating profit
NOK −505,000
▼ −90 %
Equity
NOK 211,000
▼ −71 %
Est. value
NOK 1.8m

Financial health · 2025

Liquidity
1.20
Satisfactory
Current assets ÷ current liabilities
Profitability
-39.4%
Not satisfactory
Return on total assets
Solidity
23.9%
Good
Equity as a share of total capital

Who owns GBE BYGG AS?

GBE BYGG AS
NOK 4.8m rev. · NOK −505,000 profit

GBE BYGG AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about GBE BYGG AS

Who owns GBE BYGG AS?

Besar Emini is the largest registered owner, with 50.0%.

What is the revenue of GBE BYGG AS?

GBE BYGG AS had revenue of NOK 4.8m in 2025.

Who is the general manager of GBE BYGG AS?

Gzim Emini is registered as general manager of GBE BYGG AS.

Where is GBE BYGG AS based?

GBE BYGG AS has its business address in Oslo.

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.