BIZTRAC BETA
Retail sale of articles for lighting

ELVERUM LAMPEFORRETNING AS

Org. no. 814771202 Limited company (AS) Elverum Incorporated 2015 Active
Ownership graph ↗
Revenue 2025 NOK 1.9m
Operating profit NOK −109,000
Equity NOK 306,000
Incorporated 2015
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−109k kr).

ELVERUM LAMPEFORRETNING AS is registered as a limited company in Elverum, Innlandet with organisation number 814771202. The business is classified under retail sale of articles for lighting (NACE 47.552). The company was incorporated in 2015. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Drive butikkhandel med belysningsutstyr.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.9m in revenue and NOK −109,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.9m
Operating profit
NOK −109,000
Equity
NOK 306,000
Est. value
NOK 752,000

Financial health · 2025

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

Who owns ELVERUM LAMPEFORRETNING AS?

EVEN LØKEN
ELVERUM LAMPEFORRETNING AS
NOK 1.9m rev. · NOK −109,000 profit

ELVERUM LAMPEFORRETNING AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about ELVERUM LAMPEFORRETNING AS

Who owns ELVERUM LAMPEFORRETNING AS?

EVEN LØKEN is the largest registered owner, with 50.0%.

What is the revenue of ELVERUM LAMPEFORRETNING AS?

ELVERUM LAMPEFORRETNING AS had revenue of NOK 1.9m in 2025.

Who is the general manager of ELVERUM LAMPEFORRETNING AS?

Mette Finstad is registered as general manager of ELVERUM LAMPEFORRETNING AS.

Where is ELVERUM LAMPEFORRETNING AS based?

ELVERUM LAMPEFORRETNING AS has its business address in Elverum.

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.