BIZTRAC BETA
Computer programming activities

LUXSAVE AS

Org. no. 995117169 Limited company (AS) Trondheim Incorporated 2010 Active
Ownership graph ↗
Revenue 2024 NOK 3.7m
Operating profit NOK −871,000
Equity NOK 7.9m
Incorporated 2010
Employees 6
Share capital NOK 453,000

Signals

2 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−871k kr).
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

LUXSAVE AS is registered as a limited company in Trondheim, Trøndelag with organisation number 995117169. The business is classified under computer programming activities (NACE 62.100). The company was incorporated in 2010 and has 6 registered employees. Registered share capital is NOK 453,000, divided into 452710 shares. The company's stated purpose is: “Utvikling og salg av programvare for kontroll og styring av elektriske systemer for å spare energi. Selskapet kan også erverve aksjer i andre selskap.”. The most recent filed accounts, for the 2024 financial year, show NOK 3.7m in revenue and NOK −871,000 in operating profit.

Key figures · 2024

Revenue
NOK 3.7m
Operating profit
NOK −871,000
Equity
NOK 7.9m
Est. value
NOK 9.8m

Financial health · 2024

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

Who owns LUXSAVE AS?

LUND FORVALTNING AS
LUXSAVE AS
NOK 3.7m rev. · NOK −871,000 profit

LUXSAVE AS has 14 registered shareholders:

All shareholders and roles →

Frequently asked questions about LUXSAVE AS

Who owns LUXSAVE AS?

LUND FORVALTNING AS is the largest registered owner, with 66.6%.

What is the revenue of LUXSAVE AS?

LUXSAVE AS had revenue of NOK 3.7m in 2024.

Where is LUXSAVE AS based?

LUXSAVE 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.