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

GB-BYGG AS

Org. no. 931205846 Limited company (AS) Ålesund Incorporated 2023 Active
Revenue 2025 NOK 2.4m
Operating profit NOK 220,000
Equity NOK 55,000
Incorporated 2023
Share capital NOK 30,000

Signals

1 flags
  • Nylig endring 2026-09-13 Adresseendring registrert 2026-09-13.

GB-BYGG AS is registered as a limited company in Ålesund, Møre og Romsdal with organisation number 931205846. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 2023. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Oppføring av bygninger.”. The most recent filed accounts, for the 2025 financial year, show NOK 2.4m in revenue and NOK 220,000 in operating profit.

Key figures · 2025

Revenue
NOK 2.4m
▲ +13 %
Operating profit
NOK 220,000
▲ +266 %
Equity
NOK 55,000
▲ +141 %
Est. value
NOK 531,000

Financial health · 2025

Liquidity
0.91
Weak
Current assets ÷ current liabilities
Profitability
65.6%
Very good
Return on total assets
Solidity
13.3%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns GB-BYGG AS?

GB-BYGG AS
NOK 2.4m rev. · NOK 220,000 profit

GB-BYGG AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about GB-BYGG AS

Who owns GB-BYGG AS?

Grzegorz Michal Batko is the largest registered owner, with 100.0%.

What is the revenue of GB-BYGG AS?

GB-BYGG AS had revenue of NOK 2.4m in 2025.

Who is the general manager of GB-BYGG AS?

Grzegorz Michal Batko is registered as general manager of GB-BYGG AS.

Where is GB-BYGG AS based?

GB-BYGG AS has its business address in Ålesund.

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.