BIZTRAC BETA
Computer programming activities

LILLEHAMMER TUNINGSERVICE AS

Org. no. 929241592 Limited company (AS) Gausdal Incorporated 2022 Active
Ownership graph ↗
Revenue 2024 NOK 278,000
Operating profit NOK −50,000
Equity NOK 31,000
Incorporated 2022
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−50k kr).

LILLEHAMMER TUNINGSERVICE AS is registered as a limited company in Gausdal, Innlandet with organisation number 929241592. The business is classified under computer programming activities (NACE 62.100). The company was incorporated in 2022. Registered share capital is NOK 30,000, divided into 10 shares. The company's stated purpose is: “Kjøp og salg av varer, og dertil hørende tjenester.”. The most recent filed accounts, for the 2024 financial year, show NOK 278,000 in revenue and NOK −50,000 in operating profit.

Key figures · 2024

Revenue
NOK 278,000
Operating profit
NOK −50,000
Equity
NOK 31,000
Est. value
NOK 343,000

Financial health · 2024

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

Solidity capped at Weak because equity is below NOK 100,000.

Who owns LILLEHAMMER TUNINGSERVICE AS?

KREKKES AUTOREP AS
LILLEHAMMER TUNINGSERVICE AS
NOK 278,000 rev. · NOK −50,000 profit

LILLEHAMMER TUNINGSERVICE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about LILLEHAMMER TUNINGSERVICE AS

Who owns LILLEHAMMER TUNINGSERVICE AS?

KREKKES AUTOREP AS is the largest registered owner, with 100.0%.

What is the revenue of LILLEHAMMER TUNINGSERVICE AS?

LILLEHAMMER TUNINGSERVICE AS had revenue of NOK 278,000 in 2024.

Where is LILLEHAMMER TUNINGSERVICE AS based?

LILLEHAMMER TUNINGSERVICE AS has its business address in Vestre Gausdal.

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.