BIZTRAC BETA
Rental and operating of own or leased real estate

GUMABE AS

Org. no. 989319736 Limited company (AS) Haugesund Incorporated 2005 Active
Ownership graph ↗
Revenue 2025 NOK 142,000
Operating profit NOK −189,000
Equity NOK 9.3m
Incorporated 2005
Share capital NOK 100,000

Signals

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

GUMABE AS is registered as a limited company in Haugesund, Rogaland with organisation number 989319736. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2005. Registered share capital is NOK 100,000, divided into 1000 shares. The company's stated purpose is: “Eie og forvalte aksjer og andre verdipapirer, handel og tjenesteytende virksomhet, samt hva hermed står i forbindelse, herunder å delta i andre foretak som driver tilsvarende virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 142,000 in revenue and NOK −189,000 in operating profit.

Key figures · 2025

Revenue
NOK 142,000
Operating profit
NOK −189,000
Equity
NOK 9.3m
Est. value
NOK 6.8m

Financial health · 2025

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

Who owns GUMABE AS?

BAARD SIGMUND FØRRE
GUMABE AS
NOK 142,000 rev. · NOK −189,000 profit

GUMABE AS has 1 registered shareholder:

All shareholders and roles →

Which companies does GUMABE AS own?

GUMABE AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about GUMABE AS

Who owns GUMABE AS?

BAARD SIGMUND FØRRE is the largest registered owner, with 100.0%.

What is the revenue of GUMABE AS?

GUMABE AS had revenue of NOK 142,000 in 2025.

Where is GUMABE AS based?

GUMABE AS has its business address in Haugesund.

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.