BIZTRAC BETA
Temporary employment agency activities and other human resource provisions

HAMANOR AS

Org. no. 931193996 Limited company (AS) Drammen Incorporated 2023 Active
Ownership graph ↗
Revenue 2024 NOK 495,000
Operating profit NOK 281,000
Equity NOK 244,000
Incorporated 2023
Employees 6
Share capital NOK 400,000

Signals

1 flags
  • Nylig endring 2026-04-23 Adresseendring registrert 2026-04-23.

HAMANOR AS is registered as a limited company in Drammen, Buskerud with organisation number 931193996. The business is classified under temporary employment agency activities and other human resource provisions (NACE 78.200). The company was incorporated in 2023 and has 6 registered employees. Registered share capital is NOK 400,000, divided into 400 shares. The company's stated purpose is: “Vikarformidling, personalutvelgelse, kursvirksomhet og annen virksomhet som hører under dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 495,000 in revenue and NOK 281,000 in operating profit.

Key figures · 2024

Revenue
NOK 495,000
Operating profit
NOK 281,000
Equity
NOK 244,000
Est. value
NOK 1.0m

Financial health · 2024

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

Who owns HAMANOR AS?

KARIMI HOLDING AS
HAMANOR AS
NOK 495,000 rev. · NOK 281,000 profit

HAMANOR AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about HAMANOR AS

Who owns HAMANOR AS?

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

What is the revenue of HAMANOR AS?

HAMANOR AS had revenue of NOK 495,000 in 2024.

Who is the general manager of HAMANOR AS?

Hamid Karimi is registered as general manager of HAMANOR AS.

Where is HAMANOR AS based?

HAMANOR AS has its business address in Drammen.

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.