BIZTRAC BETA
Rental and operating of own or leased real estate

HERCULES UTVIKLING AS

Org. no. 988703753 Limited company (AS) Bærum Incorporated 2005 Active
Ownership graph ↗
Revenue 2024 NOK 1.7m
Operating profit NOK 794,000
Equity NOK 3.2m
Incorporated 2005
Share capital NOK 2.5m

HERCULES UTVIKLING AS is registered as a limited company in Bærum, Akershus with organisation number 988703753. 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 2.5m, divided into 5000 shares. The company's stated purpose is: “Selskapets formål skal være kjøp og utvikling av fast eiendom samt alt som står i forbindelse med dette, herunder deltakelse i andre selskaper.”. The most recent filed accounts, for the 2024 financial year, show NOK 1.7m in revenue and NOK 794,000 in operating profit.

Key figures · 2024

Revenue
NOK 1.7m
Operating profit
NOK 794,000
Equity
NOK 3.2m
Est. value
NOK 3.7m

Financial health · 2024

Liquidity
0.15
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
18.1%
Good
Equity as a share of total capital

Who owns HERCULES UTVIKLING AS?

HERCULES HOLDING AS
HERCULES UTVIKLING AS
NOK 1.7m rev. · NOK 794,000 profit

HERCULES UTVIKLING AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about HERCULES UTVIKLING AS

Who owns HERCULES UTVIKLING AS?

HERCULES HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of HERCULES UTVIKLING AS?

HERCULES UTVIKLING AS had revenue of NOK 1.7m in 2024.

Who is the general manager of HERCULES UTVIKLING AS?

Herman Stene Cedergren is registered as general manager of HERCULES UTVIKLING AS.

Where is HERCULES UTVIKLING AS based?

HERCULES UTVIKLING AS has its business address in Snarøya.

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.