BIZTRAC BETA
Computer consultancy and computer facilities management activities

LAVRANS TECH AS

Org. no. 829576902 Limited company (AS) Asker Incorporated 2022 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −33,000
Equity NOK 21,000
Incorporated 2022
Share capital NOK 30,000

Signals

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

LAVRANS TECH AS is registered as a limited company in Asker, Akershus with organisation number 829576902. The business is classified under computer consultancy and computer facilities management activities (NACE 62.200). The company was incorporated in 2022. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Konsulentvirksomhet tilknyttet informasjonsteknologi”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −33,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −33,000
Equity
NOK 21,000
Est. value
NOK 39,000

Financial health · 2025

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

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

Who owns LAVRANS TECH AS?

LAVRANS GRID AS
LAVRANS TECH AS
NOK 0 rev. · NOK −33,000 profit

LAVRANS TECH AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about LAVRANS TECH AS

Who owns LAVRANS TECH AS?

LAVRANS GRID AS is the largest registered owner, with 100.0%.

What is the revenue of LAVRANS TECH AS?

LAVRANS TECH AS had revenue of NOK 0 in 2025.

Who is the general manager of LAVRANS TECH AS?

Jo Lavrans Krokengen is registered as general manager of LAVRANS TECH AS.

Where is LAVRANS TECH AS based?

LAVRANS TECH AS has its business address in Billingstad.

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.