BIZTRAC BETA
Industrial product and fashion design activities

NAVITAS NORDICS AS

Org. no. 928906108 Limited company (AS) Oslo Incorporated 2022 Active
Ownership graph ↗
Revenue 2024 NOK 19.3m
Operating profit NOK 192,000
Equity NOK 1.1m
Incorporated 2022
Share capital NOK 30,000

Signals

1 flags
  • Nylig endring 2026-07-07 Adresseendring registrert 2026-07-07.

NAVITAS NORDICS AS is registered as a limited company in Oslo, Oslo with organisation number 928906108. The business is classified under industrial product and fashion design activities (NACE 74.110). The company was incorporated in 2022. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Tjenester innenfor design, rådgivning, prosjektering og assistansehjelp til igangkjøring knyttet til mekaniske installasjoner.”. The most recent filed accounts, for the 2024 financial year, show NOK 19.3m in revenue and NOK 192,000 in operating profit.

Key figures · 2024

Revenue
NOK 19.3m
Operating profit
NOK 192,000
Equity
NOK 1.1m
Est. value
NOK 1.2m

Financial health · 2024

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

Who owns NAVITAS NORDICS AS?

BLC NAVITAS LDA
NAVITAS NORDICS AS
NOK 19.3m rev. · NOK 192,000 profit

NAVITAS NORDICS AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about NAVITAS NORDICS AS

Who owns NAVITAS NORDICS AS?

BLC NAVITAS LDA is the largest registered owner, with 80.0%.

What is the revenue of NAVITAS NORDICS AS?

NAVITAS NORDICS AS had revenue of NOK 19.3m in 2024.

Who is the general manager of NAVITAS NORDICS AS?

Carlos Pires Eurico Lisboa is registered as general manager of NAVITAS NORDICS AS.

Where is NAVITAS NORDICS AS based?

NAVITAS NORDICS AS has its business address in Oslo.

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.