BIZTRAC BETA
Computer consultancy and computer facilities management activities

LAVIDA CONSULTING AS

Org. no. 982797128 Limited company (AS) Moss Incorporated 2000 Active
Ownership graph ↗
Revenue 2025 NOK 443,000
Operating profit NOK −129,000
Equity NOK 640,000
Incorporated 2000
Share capital NOK 100,000

Signals

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

LAVIDA CONSULTING AS is registered as a limited company in Moss, Østfold with organisation number 982797128. The business is classified under computer consultancy and computer facilities management activities (NACE 62.200). The company was incorporated in 2000. Registered share capital is NOK 100,000, divided into 1000 shares. The company's stated purpose is: “Konsulenttjenester innen IT.”. The most recent filed accounts, for the 2025 financial year, show NOK 443,000 in revenue and NOK −129,000 in operating profit.

Key figures · 2025

Revenue
NOK 443,000
Operating profit
NOK −129,000
Equity
NOK 640,000
Est. value
NOK 1.0m

Financial health · 2025

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

Who owns LAVIDA CONSULTING AS?

BJØRN THORE HYTTEN
LAVIDA CONSULTING AS
NOK 443,000 rev. · NOK −129,000 profit

LAVIDA CONSULTING AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about LAVIDA CONSULTING AS

Who owns LAVIDA CONSULTING AS?

BJØRN THORE HYTTEN is the largest registered owner, with 100.0%.

What is the revenue of LAVIDA CONSULTING AS?

LAVIDA CONSULTING AS had revenue of NOK 443,000 in 2025.

Who is the general manager of LAVIDA CONSULTING AS?

Bjørn Thore Hytten is registered as general manager of LAVIDA CONSULTING AS.

Where is LAVIDA CONSULTING AS based?

LAVIDA CONSULTING AS has its business address in Moss.

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.