BIZTRAC BETA
Computer consultancy and computer facilities management activities

LEPUS CONSULTING AS

Org. no. 935559928 Limited company (AS) Drammen Incorporated 2025 Active
Ownership graph ↗
Revenue 2025 NOK 164,000
Operating profit NOK 93,000
Equity NOK 96,000
Incorporated 2025
Share capital NOK 30,000

LEPUS CONSULTING AS is registered as a limited company in Drammen, Buskerud with organisation number 935559928. 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 30000 shares. The company's stated purpose is: “Salg av konsulenttjenester og varer innen IT.”. The most recent filed accounts, for the 2025 financial year, show NOK 164,000 in revenue and NOK 93,000 in operating profit.

Key figures · 2025

Revenue
NOK 164,000
Operating profit
NOK 93,000
Equity
NOK 96,000
Est. value
NOK 362,000

Financial health · 2025

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

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

Who owns LEPUS CONSULTING AS?

COHORS LEPORUM AS
LEPUS CONSULTING AS
NOK 164,000 rev. · NOK 93,000 profit

LEPUS CONSULTING AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about LEPUS CONSULTING AS

Who owns LEPUS CONSULTING AS?

COHORS LEPORUM AS is the largest registered owner, with 100.0%.

What is the revenue of LEPUS CONSULTING AS?

LEPUS CONSULTING AS had revenue of NOK 164,000 in 2025.

Who is the general manager of LEPUS CONSULTING AS?

Arne Alexander Arnardo Haase is registered as general manager of LEPUS CONSULTING AS.

Where is LEPUS CONSULTING AS based?

LEPUS CONSULTING AS has its business address in Mjøndalen.

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.