BIZTRAC BETA
Business and other management consultancy activities

LØVÅS KONSULENTTJENESTER AS

Org. no. 931385445 Limited company (AS) Vestre Toten Incorporated 2023 Active
Ownership graph ↗
Revenue 2025 NOK 2.9m
Operating profit NOK 2.8m
Equity NOK 3.1m
Incorporated 2023
Share capital NOK 30,000

LØVÅS KONSULENTTJENESTER AS is registered as a limited company in Vestre Toten, Innlandet with organisation number 931385445. The business is classified under business and other management consultancy activities (NACE 70.200). The company was incorporated in 2023. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Konsulenttjenester innenfor innkjøp, logistikk og tekniske fag.”. The most recent filed accounts, for the 2025 financial year, show NOK 2.9m in revenue and NOK 2.8m in operating profit.

Key figures · 2025

Revenue
NOK 2.9m
Operating profit
NOK 2.8m
Equity
NOK 3.1m
Est. value
NOK 11.0m

Financial health · 2024

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

Who owns LØVÅS KONSULENTTJENESTER AS?

VEGARD VALHEIM
LØVÅS KONSULENTTJENESTER AS
NOK 2.9m rev. · NOK 2.8m profit

LØVÅS KONSULENTTJENESTER AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about LØVÅS KONSULENTTJENESTER AS

Who owns LØVÅS KONSULENTTJENESTER AS?

VEGARD VALHEIM is the largest registered owner, with 50.0%.

What is the revenue of LØVÅS KONSULENTTJENESTER AS?

LØVÅS KONSULENTTJENESTER AS had revenue of NOK 2.9m in 2025.

Who is the general manager of LØVÅS KONSULENTTJENESTER AS?

Grete Engelien Valheim is registered as general manager of LØVÅS KONSULENTTJENESTER AS.

Where is LØVÅS KONSULENTTJENESTER AS based?

LØVÅS KONSULENTTJENESTER AS has its business address in Raufoss.

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.