BIZTRAC BETA
Computer programming activities

LISSA & CO AS

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

Signals

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

LISSA & CO AS is registered as a limited company in Oslo, Oslo with organisation number 913487966. 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: “Konsulenttjenester samt investeringer i aksjer, fast eiendom og andre formuesgjenstander, herunder kjøp, salg og utleie av disse.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −18,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −18,000
Equity
NOK 2.3m
Est. value
NOK 4.2m

Financial health · 2024

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

Who owns LISSA & CO AS?

JONAS LISGÅRD
LISSA & CO AS
NOK 0 rev. · NOK −18,000 profit

LISSA & CO AS has 1 registered shareholder:

All shareholders and roles →

Which companies does LISSA & CO AS own?

LISSA & CO AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about LISSA & CO AS

Who owns LISSA & CO AS?

JONAS LISGÅRD is the largest registered owner, with 100.0%.

What is the revenue of LISSA & CO AS?

LISSA & CO AS had revenue of NOK 0 in 2024.

Who is the general manager of LISSA & CO AS?

Jonas Lisgård is registered as general manager of LISSA & CO AS.

Where is LISSA & CO AS based?

LISSA & CO 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.