BIZTRAC BETA
Business and other management consultancy activities

KASO AS

Org. no. 889207752 Limited company (AS) Lillestrøm Incorporated 2005 Active
Ownership graph ↗
Revenue 2025 NOK 1.0m
Operating profit NOK 226,000
Equity NOK 470,000
Incorporated 2005
Share capital NOK 100,000

KASO AS is registered as a limited company in Lillestrøm, Akershus with organisation number 889207752. The business is classified under business and other management consultancy activities (NACE 70.200). The company was incorporated in 2005. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Omfatte konsulenttjenester, bedriftsrådgivning, snekkertjenester, serviceoppgaver, lagerarbeid, pakking, henting, sortering, transport og bringing (nasjonalt og internasjonalt) av brevpost og postpakker og kolli utført av virksomheten. Aktiviteten kan foregå ved både privat og offentlig transport.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.0m in revenue and NOK 226,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.0m
Operating profit
NOK 226,000
Equity
NOK 470,000
Est. value
NOK 1.2m

Financial health · 2025

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

Who owns KASO AS?

KJELL ARNE LYRSTAD
KASO AS
NOK 1.0m rev. · NOK 226,000 profit

KASO AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about KASO AS

Who owns KASO AS?

KJELL ARNE LYRSTAD is the largest registered owner, with 100.0%.

What is the revenue of KASO AS?

KASO AS had revenue of NOK 1.0m in 2025.

Who is the general manager of KASO AS?

Kjell Arne Lyrstad is registered as general manager of KASO AS.

Where is KASO AS based?

KASO AS has its business address in Strømmen.

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.