BIZTRAC BETA
Business and other management consultancy activities

LEAN COMMUNICATIONS AS

Org. no. 928708500 Limited company (AS) Oslo Incorporated 2022 Active
Ownership graph ↗
Revenue 2024 NOK 12.8m
Operating profit NOK 625,000
Equity NOK 738,000
Incorporated 2022
Employees 20
Share capital NOK 60,000

LEAN COMMUNICATIONS AS is registered as a limited company in Oslo, Oslo with organisation number 928708500. The business is classified under business and other management consultancy activities (NACE 70.200). The company was incorporated in 2022 and has 20 registered employees. Registered share capital is NOK 60,000, divided into 30000 shares. The company's stated purpose is: “Bedriftsrådgivning, herunder strategi og implementering av produksjonsoptimaliserende tiltak.”. The most recent filed accounts, for the 2024 financial year, show NOK 12.8m in revenue and NOK 625,000 in operating profit.

Key figures · 2024

Revenue
NOK 12.8m
Operating profit
NOK 625,000
Equity
NOK 738,000
Est. value
NOK 2.9m

Financial health · 2024

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

Who owns LEAN COMMUNICATIONS AS?

TØIEN HOLDING AS
LEAN COMMUNICATIONS AS
NOK 12.8m rev. · NOK 625,000 profit

LEAN COMMUNICATIONS AS has 6 registered shareholders:

All shareholders and roles →

Frequently asked questions about LEAN COMMUNICATIONS AS

Who owns LEAN COMMUNICATIONS AS?

TØIEN HOLDING AS is the largest registered owner, with 30.0%.

What is the revenue of LEAN COMMUNICATIONS AS?

LEAN COMMUNICATIONS AS had revenue of NOK 12.8m in 2024.

Who is the general manager of LEAN COMMUNICATIONS AS?

Bjørn Einar Aga is registered as general manager of LEAN COMMUNICATIONS AS.

Where is LEAN COMMUNICATIONS AS based?

LEAN COMMUNICATIONS 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.