BIZTRAC BETA
Rental and operating of own or leased real estate

GUMMI-CENTRALEN EIENDOM AS

Org. no. 940732778 Limited company (AS) Asker Incorporated 1986 Active
Ownership graph ↗
Revenue 2024 NOK 2.8m
Operating profit NOK 2.2m
Equity NOK 4.4m
Incorporated 1986
Share capital NOK 3.7m

GUMMI-CENTRALEN EIENDOM AS is registered as a limited company in Asker, Akershus with organisation number 940732778. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 1986. Registered share capital is NOK 3.7m, divided into 3737533 shares. The company's stated purpose is: “Investering i og utleie av fast eiendom.”. The most recent filed accounts, for the 2024 financial year, show NOK 2.8m in revenue and NOK 2.2m in operating profit.

Key figures · 2024

Revenue
NOK 2.8m
Operating profit
NOK 2.2m
Equity
NOK 4.4m
Est. value
NOK 7.4m

Financial health · 2024

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

Who owns GUMMI-CENTRALEN EIENDOM AS?

TAFJORD AS
GUMMI-CENTRALEN EIENDOM AS
NOK 2.8m rev. · NOK 2.2m profit

GUMMI-CENTRALEN EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Group structure

GUMMI-CENTRALEN EIENDOM AS er morselskap for 1 datterselskap:

Frequently asked questions about GUMMI-CENTRALEN EIENDOM AS

Who owns GUMMI-CENTRALEN EIENDOM AS?

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

What is the revenue of GUMMI-CENTRALEN EIENDOM AS?

GUMMI-CENTRALEN EIENDOM AS had revenue of NOK 2.8m in 2024.

Who is the general manager of GUMMI-CENTRALEN EIENDOM AS?

Jon Tafjord is registered as general manager of GUMMI-CENTRALEN EIENDOM AS.

Where is GUMMI-CENTRALEN EIENDOM AS based?

GUMMI-CENTRALEN EIENDOM AS has its business address in Asker.

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.