BIZTRAC BETA
Activities of employment placement agencies

LR ARNESEN CONSULTING AS

Org. no. 930050830 Limited company (AS) Fredrikstad Incorporated 2022 Active
Ownership graph ↗
Revenue 2025 NOK 1.5m
Operating profit NOK 136,000
Equity NOK 328,000
Incorporated 2022
Share capital NOK 30,000

LR ARNESEN CONSULTING AS is registered as a limited company in Fredrikstad, Østfold with organisation number 930050830. The business is classified under activities of employment placement agencies (NACE 78.100). The company was incorporated in 2022. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Rekrutteringsbransjen: Konsulenttjenester og kurs knyttet til rekruttering og karriererådgiving/omstilling.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.5m in revenue and NOK 136,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.5m
Operating profit
NOK 136,000
Equity
NOK 328,000
Est. value
NOK 752,000

Financial health · 2025

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

Who owns LR ARNESEN CONSULTING AS?

LEIF RUNE ARNESEN
LR ARNESEN CONSULTING AS
NOK 1.5m rev. · NOK 136,000 profit

LR ARNESEN CONSULTING AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about LR ARNESEN CONSULTING AS

Who owns LR ARNESEN CONSULTING AS?

LEIF RUNE ARNESEN is the largest registered owner, with 100.0%.

What is the revenue of LR ARNESEN CONSULTING AS?

LR ARNESEN CONSULTING AS had revenue of NOK 1.5m in 2025.

Who is the general manager of LR ARNESEN CONSULTING AS?

Leif Rune Arnesen is registered as general manager of LR ARNESEN CONSULTING AS.

Where is LR ARNESEN CONSULTING AS based?

LR ARNESEN CONSULTING AS has its business address in Kråkerøy.

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.