BIZTRAC BETA
Business and other management consultancy activities

HR-PARTNER AS

Org. no. 927280094 Limited company (AS) Stjørdal Incorporated 2021 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −1,000
Equity NOK 19,000
Incorporated 2021
Share capital NOK 30,000

Signals

2 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−1k kr).
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

HR-PARTNER AS is registered as a limited company in Stjørdal, Trøndelag with organisation number 927280094. The business is classified under business and other management consultancy activities (NACE 70.200). The company was incorporated in 2021. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Salg av tjenester tilknyttet HR og personalarbeid og annet som står i naturlig forbindelse med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −1,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −1,000
Equity
NOK 19,000
Est. value
NOK 32,000

Financial health · 2025

Liquidity
Not available
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
100.0%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns HR-PARTNER AS?

EIKA ØKONOMI MIDT-NORGE AS
HR-PARTNER AS
NOK 0 rev. · NOK −1,000 profit

HR-PARTNER AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about HR-PARTNER AS

Who owns HR-PARTNER AS?

EIKA ØKONOMI MIDT-NORGE AS is the largest registered owner, with 100.0%.

What is the revenue of HR-PARTNER AS?

HR-PARTNER AS had revenue of NOK 0 in 2025.

Where is HR-PARTNER AS based?

HR-PARTNER AS has its business address in Hegra.

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.