biztrac. BETA
COMPANY REGISTER PROFILE
929038215 ORG. NO. 2024 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Computer programming activities

HLPR AS

Org. no. 929038215 Limited company (AS) Bærum Incorporated 2022 Active
Ownership graph ↗
Revenue 2024 NOK 507,000
Operating profit NOK 80,000
Equity NOK 25,000
Incorporated 2022
Share capital NOK 30,000

HLPR AS is registered as a limited company in Bærum, Akershus with organisation number 929038215. The business is classified under computer programming activities (NACE 62.100). The company was incorporated in 2022. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Selge tjenester og varer innen digitale tjenesterog annet som naturlig sammenfaller med dette, samt deltakelse i andre selskaper, investeringer og nærliggende virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 507,000 in revenue and NOK 80,000 in operating profit.

Key figures · 2024

Revenue
NOK 507,000
▲ +7 %
Operating profit
NOK 80,000
▼ −83 %
Equity
NOK 25,000
▼ −17 %
Est. value
NOK 744,000

Financial health · 2024

Liquidity
0.99
Weak
Current assets ÷ current liabilities
Profitability
27.6%
Very good
Return on total assets
Solidity
4.5%
Weak
Equity as a share of total capital

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

Who owns HLPR AS?

HLPR AS
NOK 507,000 rev. · NOK 80,000 profit

HLPR AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about HLPR AS

Who owns HLPR AS?

Bjørn Christian Riborg is the largest registered owner, with 100.0%.

What is the revenue of HLPR AS?

HLPR AS had revenue of NOK 507,000 in 2024.

Who is the general manager of HLPR AS?

Bjørn Christian Riborg is registered as general manager of HLPR AS.

Where is HLPR AS based?

HLPR AS has its business address in Bekkestua.

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

Report a problem

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