BIZTRAC BETA
Retail sale of articles for lighting

VÆRNESS ELEKTRISK AS

Org. no. 817249612 Limited company (AS) Trondheim Incorporated 1969 Active
Ownership graph ↗
Revenue 2024 NOK 14.4m
Operating profit NOK 188,000
Equity NOK 7.1m
Incorporated 1969
Employees 8
Share capital NOK 100,000

VÆRNESS ELEKTRISK AS is registered as a limited company in Trondheim, Trøndelag with organisation number 817249612. The business is classified under retail sale of articles for lighting (NACE 47.552). The company was incorporated in 1969 and has 8 registered employees. Registered share capital is NOK 100,000. The company's stated purpose is: “Handel, samt ved aksjetegning, lån eller på annen måte gjøre seg interessert i andre selskaper. Videre er formålet å drive engros-virksomhet og ta opp tekniske agenturer.”. The most recent filed accounts, for the 2024 financial year, show NOK 14.4m in revenue and NOK 188,000 in operating profit.

Key figures · 2024

Revenue
NOK 14.4m
Operating profit
NOK 188,000
Equity
NOK 7.1m
Est. value
NOK 4.4m

Financial health · 2024

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

Who owns VÆRNESS ELEKTRISK AS?

NABO EIENDOM AS
VÆRNESS ELEKTRISK AS
NOK 14.4m rev. · NOK 188,000 profit

VÆRNESS ELEKTRISK AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about VÆRNESS ELEKTRISK AS

Who owns VÆRNESS ELEKTRISK AS?

NABO EIENDOM AS is the largest registered owner, with 65.0%.

What is the revenue of VÆRNESS ELEKTRISK AS?

VÆRNESS ELEKTRISK AS had revenue of NOK 14.4m in 2024.

Who is the general manager of VÆRNESS ELEKTRISK AS?

Narve Altern is registered as general manager of VÆRNESS ELEKTRISK AS.

Where is VÆRNESS ELEKTRISK AS based?

VÆRNESS ELEKTRISK AS has its business address in Trondheim.

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.