BIZTRAC BETA
COMPANY REGISTER PROFILE
913671619 ORG. NO. 2024 ACCOUNTS 7 SECTIONS
Active UPDATED 15.06.2026
Computer consultancy and computer facilities management activities

LEANWAY AS

Org. no. 913671619 Limited company (AS) Oslo Incorporated 2014 Active
Ownership graph ↗
Revenue 2024 NOK 124,000
Operating profit NOK 29,000
Equity NOK 1.1m
Incorporated 2014
Share capital NOK 30,000

LEANWAY AS is registered as a limited company in Oslo, Oslo with organisation number 913671619. The business is classified under computer consultancy and computer facilities management activities (NACE 62.200). The company was incorporated in 2014. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Konsulentvirksomhet tilknyttet informasjonsteknologi og andre produkter/tjenester som naturlig hører sammen med dette, herunder å delta i andre selskap med lignende virksomhet og kjøp og salg av aksjer eller på annen måte gjøre seg interessert i andre foretak.”. The most recent filed accounts, for the 2024 financial year, show NOK 124,000 in revenue and NOK 29,000 in operating profit.

Key figures · 2024

Revenue
NOK 124,000
Operating profit
NOK 29,000
Equity
NOK 1.1m
Est. value
NOK 725,000

Financial health · 2024

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

Who owns LEANWAY AS?

NIKLAS ERIK BJÖRNERSTEDT
LEANWAY AS
NOK 124,000 rev. · NOK 29,000 profit

LEANWAY AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about LEANWAY AS

Who owns LEANWAY AS?

NIKLAS ERIK BJÖRNERSTEDT is the largest registered owner, with 100.0%.

What is the revenue of LEANWAY AS?

LEANWAY AS had revenue of NOK 124,000 in 2024.

Where is LEANWAY AS based?

LEANWAY 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.