BIZTRAC BETA
Computer consultancy and computer facilities management activities

LØGE CONSULTING AS

Org. no. 920287573 Limited company (AS) Stavanger Incorporated 2018 Active
Ownership graph ↗
Revenue 2025 NOK 600
Operating profit NOK −10,000
Equity NOK 10,000
Incorporated 2018
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−10k kr).

LØGE CONSULTING AS is registered as a limited company in Stavanger, Rogaland with organisation number 920287573. The business is classified under computer consultancy and computer facilities management activities (NACE 62.200). The company was incorporated in 2018. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Konsulenttjenester innen informasjonsteknologi, samt drift og utvikling av egne og andre selskapers digitale løsninger.”. The most recent filed accounts, for the 2025 financial year, show NOK 600 in revenue and NOK −10,000 in operating profit.

Key figures · 2025

Revenue
NOK 600
Operating profit
NOK −10,000
Equity
NOK 10,000
Est. value
NOK 6,000

Financial health · 2025

Liquidity
1.38
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
27.6%
Weak
Equity as a share of total capital

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

Who owns LØGE CONSULTING AS?

LØGE HOLDING AS
LØGE CONSULTING AS
NOK 600 rev. · NOK −10,000 profit

LØGE CONSULTING AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about LØGE CONSULTING AS

Who owns LØGE CONSULTING AS?

LØGE HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of LØGE CONSULTING AS?

LØGE CONSULTING AS had revenue of NOK 600 in 2025.

Where is LØGE CONSULTING AS based?

LØGE CONSULTING AS has its business address in Stavanger.

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.