BIZTRAC BETA
Buying and selling of own real estate

HESSELBERG EIENDOM MOSS AS

Org. no. 912293254 Limited company (AS) Lillestrøm Incorporated 2013 Active
Ownership graph ↗
Revenue 2024 NOK 1.5m
Operating profit NOK 158,000
Equity NOK 2.2m
Incorporated 2013
Share capital NOK 1.8m

HESSELBERG EIENDOM MOSS AS is registered as a limited company in Lillestrøm, Akershus with organisation number 912293254. The business is classified under buying and selling of own real estate (NACE 68.110). The company was incorporated in 2013. Registered share capital is NOK 1.8m, divided into 100 shares. The company's stated purpose is: “Kjøp, salg og utvikling av eiendom samt deltakelse i, eventuelt overtakelse av, andre selskaper.”. The most recent filed accounts, for the 2024 financial year, show NOK 1.5m in revenue and NOK 158,000 in operating profit.

Key figures · 2024

Revenue
NOK 1.5m
Operating profit
NOK 158,000
Equity
NOK 2.2m
Est. value
NOK 1.8m

Financial health · 2024

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

Who owns HESSELBERG EIENDOM MOSS AS?

AS SIGURD HESSELBERG
HESSELBERG EIENDOM MOSS AS
NOK 1.5m rev. · NOK 158,000 profit

HESSELBERG EIENDOM MOSS AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about HESSELBERG EIENDOM MOSS AS

Who owns HESSELBERG EIENDOM MOSS AS?

AS SIGURD HESSELBERG is the largest registered owner, with 100.0%.

What is the revenue of HESSELBERG EIENDOM MOSS AS?

HESSELBERG EIENDOM MOSS AS had revenue of NOK 1.5m in 2024.

Who is the general manager of HESSELBERG EIENDOM MOSS AS?

Andreas Corwin is registered as general manager of HESSELBERG EIENDOM MOSS AS.

Where is HESSELBERG EIENDOM MOSS AS based?

HESSELBERG EIENDOM MOSS AS has its business address in Frogner.

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.