BIZTRAC BETA
Accounting and bookkeeping

HEDENSTAD & CO AS

Org. no. 953050900 Limited company (AS) Bærum Incorporated 1989 Active
Ownership graph ↗
Revenue 2024 NOK 242,000
Operating profit NOK 150,000
Equity NOK 2.1m
Incorporated 1989
Share capital NOK 50,000

HEDENSTAD & CO AS is registered as a limited company in Bærum, Akershus with organisation number 953050900. The business is classified under accounting and bookkeeping (NACE 69.202). The company was incorporated in 1989. Registered share capital is NOK 50,000, divided into 50 shares. The company's stated purpose is: “Konsulentvirksomhet innen økonomi og regnskap samt deltagelse i andre selskaper og alt hva dermed står i forbindelse.”. The most recent filed accounts, for the 2024 financial year, show NOK 242,000 in revenue and NOK 150,000 in operating profit.

Key figures · 2024

Revenue
NOK 242,000
Operating profit
NOK 150,000
Equity
NOK 2.1m
Est. value
NOK 1.4m

Financial health · 2024

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

Who owns HEDENSTAD & CO AS?

RAGNAR HEDENSTAD
HEDENSTAD & CO AS
NOK 242,000 rev. · NOK 150,000 profit

HEDENSTAD & CO AS has 1 registered shareholder:

All shareholders and roles →

Which companies does HEDENSTAD & CO AS own?

HEDENSTAD & CO AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about HEDENSTAD & CO AS

Who owns HEDENSTAD & CO AS?

RAGNAR HEDENSTAD is the largest registered owner, with 100.0%.

What is the revenue of HEDENSTAD & CO AS?

HEDENSTAD & CO AS had revenue of NOK 242,000 in 2024.

Who is the general manager of HEDENSTAD & CO AS?

Ragnar Hedenstad is registered as general manager of HEDENSTAD & CO AS.

Where is HEDENSTAD & CO AS based?

HEDENSTAD & CO AS has its business address in Høvik.

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.