BIZTRAC BETA
Publishing of journals and periodicals

GJESDALBUEN AS

Org. no. 976204611 Limited company (AS) Gjesdal Incorporated 1996 Active
Ownership graph ↗
Revenue 2024 NOK 10.5m
Operating profit NOK 310,000
Equity NOK 7.1m
Incorporated 1996
Employees 6
Share capital NOK 200,000

GJESDALBUEN AS is registered as a limited company in Gjesdal, Rogaland with organisation number 976204611. The business is classified under publishing of journals and periodicals (NACE 58.130). The company was incorporated in 1996 and has 6 registered employees. Registered share capital is NOK 200,000. The company's stated purpose is: “Lage og utgi avis, samt salg av trykksaker og kontorrekv.”. The most recent filed accounts, for the 2024 financial year, show NOK 10.5m in revenue and NOK 310,000 in operating profit.

Key figures · 2024

Revenue
NOK 10.5m
Operating profit
NOK 310,000
Equity
NOK 7.1m
Est. value
NOK 5.8m

Financial health · 2024

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

Who owns GJESDALBUEN AS?

AMEDIA NORGE AS
GJESDALBUEN AS
NOK 10.5m rev. · NOK 310,000 profit

GJESDALBUEN AS has 1 registered shareholder:

All shareholders and roles →

Which companies does GJESDALBUEN AS own?

GJESDALBUEN AS holds a stake in 1 company:

See the full ownership structure →

Group structure

GJESDALBUEN AS er morselskap for 74 datterselskaper:

Frequently asked questions about GJESDALBUEN AS

Who owns GJESDALBUEN AS?

AMEDIA NORGE AS is the largest registered owner, with 100.0%.

What is the revenue of GJESDALBUEN AS?

GJESDALBUEN AS had revenue of NOK 10.5m in 2024.

Who is the general manager of GJESDALBUEN AS?

Eugen Hammer is registered as general manager of GJESDALBUEN AS.

Where is GJESDALBUEN AS based?

GJESDALBUEN AS has its business address in Ålgård.

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.