BIZTRAC BETA
Computer programming activities

LAYZIT AS

Org. no. 913157745 Limited company (AS) Oslo Incorporated 2014 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −18,000
Equity NOK 1.4m
Incorporated 2014
Share capital NOK 30,000

Signals

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

LAYZIT AS is registered as a limited company in Oslo, Oslo with organisation number 913157745. The business is classified under computer programming activities (NACE 62.100). The company was incorporated in 2014. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Support, drift og utvikling av dataløsninger, kjøp, salg og drift av fast eiendom samt kjøp av aksjer eller på annen måte delta i andre virksomheter.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −18,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −18,000
Equity
NOK 1.4m
Est. value
NOK 653,000

Financial health · 2025

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

Who owns LAYZIT AS?

LARS SMØRÅS HØYSÆTER
LAYZIT AS
NOK 0 rev. · NOK −18,000 profit

LAYZIT AS has 1 registered shareholder:

All shareholders and roles →

Which companies does LAYZIT AS own?

LAYZIT AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about LAYZIT AS

Who owns LAYZIT AS?

LARS SMØRÅS HØYSÆTER is the largest registered owner, with 100.0%.

What is the revenue of LAYZIT AS?

LAYZIT AS had revenue of NOK 0 in 2025.

Who is the general manager of LAYZIT AS?

Lars Smørås Høysæter is registered as general manager of LAYZIT AS.

Where is LAYZIT AS based?

LAYZIT AS has its business address in Oslo.

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.