BIZTRAC BETA
COMPANY REGISTER PROFILE
921687095 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 02.09.2026
Temporary employment agency activities and other human resource provisions

HARDSJØ 2 AS

Org. no. 921687095 Limited company (AS) Austevoll Incorporated 2018 Active
Ownership graph ↗
Revenue 2025 NOK 4.6m
Operating profit NOK 177,000
Equity NOK 1.7m
Incorporated 2018
Share capital NOK 32,000

Signals

1 flags
  • Nylig endring 2026-08-25 Avregistrert registrert 2026-08-25.

HARDSJØ 2 AS is registered as a limited company in Austevoll, Vestland with organisation number 921687095. The business is classified under temporary employment agency activities and other human resource provisions (NACE 78.200). The company was incorporated in 2018. Registered share capital is NOK 32,000, divided into 30 shares. The company's stated purpose is: “Utleie av personalet.”. The most recent filed accounts, for the 2025 financial year, show NOK 4.6m in revenue and NOK 177,000 in operating profit.

Key figures · 2025

Revenue
NOK 4.6m
▼ −11 %
Operating profit
NOK 177,000
▲ +575 %
Equity
NOK 1.7m
▲ +11 %
Est. value
NOK 1.7m

Financial health · 2025

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

Who owns HARDSJØ 2 AS?

HARDSJØ 2 AS
NOK 4.6m rev. · NOK 177,000 profit

HARDSJØ 2 AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about HARDSJØ 2 AS

Who owns HARDSJØ 2 AS?

EIKELY INVESTERING AS is the largest registered owner, with 60.6%.

What is the revenue of HARDSJØ 2 AS?

HARDSJØ 2 AS had revenue of NOK 4.6m in 2025.

Who is the general manager of HARDSJØ 2 AS?

Øyvind Andersen is registered as general manager of HARDSJØ 2 AS.

Where is HARDSJØ 2 AS based?

HARDSJØ 2 AS has its business address in Bekkjarvik.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 02.09.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.