BIZTRAC BETA
Retail sale of motor vehicles

INVIGO AS

Org. no. 927891204 Limited company (AS) Drammen Incorporated 2021 Active
Ownership graph ↗
Revenue 2025 NOK 12.0m
Operating profit NOK 440,000
Equity NOK 2.3m
Incorporated 2021
Share capital NOK 30,000

INVIGO AS is registered as a limited company in Drammen, Buskerud with organisation number 927891204. The business is classified under retail sale of motor vehicles (NACE 47.810). The company was incorporated in 2021. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Å importere, kjøpe, distribuere, selge, eksportere, leie, yte service, vedlikeholde og reparere biler/motorsykel/båt osv. Kjøp og salg av bildeler og reparasjon, service, vedlikehold av motorvogner/person og vare kjøretøy. Og andre produkter/tjenester som naturlig hører sammen med dette og, samt kjøp og salg av aksjer og deltakelse i andre selskaper.”. The most recent filed accounts, for the 2025 financial year, show NOK 12.0m in revenue and NOK 440,000 in operating profit.

Key figures · 2025

Revenue
NOK 12.0m
Operating profit
NOK 440,000
Equity
NOK 2.3m
Est. value
NOK 3.2m

Financial health · 2025

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

Who owns INVIGO AS?

RAMUNAS RUSECKAS
INVIGO AS
NOK 12.0m rev. · NOK 440,000 profit

INVIGO AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about INVIGO AS

Who owns INVIGO AS?

RAMUNAS RUSECKAS is the largest registered owner, with 100.0%.

What is the revenue of INVIGO AS?

INVIGO AS had revenue of NOK 12.0m in 2025.

Who is the general manager of INVIGO AS?

Ramunas Ruseckas is registered as general manager of INVIGO AS.

Where is INVIGO AS based?

INVIGO AS has its business address in Krokstadelva.

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.