BIZTRAC BETA
Computer consultancy and computer facilities management activities

LE JORDAN AS

Org. no. 935607159 Limited company (AS) Drammen Incorporated 2025 Active
Ownership graph ↗
Revenue 2025 NOK 647,000
Operating profit NOK 395,000
Equity NOK 331,000
Incorporated 2025
Share capital NOK 30,000

Signals

1 flags
  • Nylig endring 2026-02-25 Adresseendring registrert 2026-02-25.

LE JORDAN AS is registered as a limited company in Drammen, Buskerud with organisation number 935607159. The business is classified under computer consultancy and computer facilities management activities (NACE 62.200). The company was incorporated in 2025. Registered share capital is NOK 30,000, divided into 10000 shares. The company's stated purpose is: “Å tilby tjenester innen prosjektledelse, konsulentvirksomhet, drift, interimfunksjoner, IT-tjenester og bedriftsrådgivning, samt annet som naturlig hører sammen med dette, og kjøp og salg av aksjer eller på annen måte gjøre seg interessert i andre foretak.”. The most recent filed accounts, for the 2025 financial year, show NOK 647,000 in revenue and NOK 395,000 in operating profit.

Key figures · 2025

Revenue
NOK 647,000
Operating profit
NOK 395,000
Equity
NOK 331,000
Est. value
NOK 1.4m

Financial health · 2025

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

Who owns LE JORDAN AS?

LEIF ERIK JORDAN
LE JORDAN AS
NOK 647,000 rev. · NOK 395,000 profit

LE JORDAN AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about LE JORDAN AS

Who owns LE JORDAN AS?

LEIF ERIK JORDAN is the largest registered owner, with 100.0%.

What is the revenue of LE JORDAN AS?

LE JORDAN AS had revenue of NOK 647,000 in 2025.

Where is LE JORDAN AS based?

LE JORDAN AS has its business address in Solbergmoen.

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.