BIZTRAC BETA
Computer consultancy and computer facilities management activities

SANSA CONSULTING AS

Org. no. 915936571 Limited company (AS) Lier Incorporated 2015 Active
Ownership graph ↗
Revenue 2025 NOK 161,000
Operating profit NOK 17,000
Equity NOK 142,000
Incorporated 2015
Share capital NOK 30,000

SANSA CONSULTING AS is registered as a limited company in Lier, Buskerud with organisation number 915936571. The business is classified under computer consultancy and computer facilities management activities (NACE 62.200). The company was incorporated in 2015. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Å drive konsulentvirksomhet innen prosjektledelse IT, rådgivning IT, teknisk infrastruktur og utvikling av informasjonssystemer.”. The most recent filed accounts, for the 2025 financial year, show NOK 161,000 in revenue and NOK 17,000 in operating profit.

Key figures · 2025

Revenue
NOK 161,000
Operating profit
NOK 17,000
Equity
NOK 142,000
Est. value
NOK 164,000

Financial health · 2025

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

Who owns SANSA CONSULTING AS?

ASISA INVEST AS
SANSA CONSULTING AS
NOK 161,000 rev. · NOK 17,000 profit

SANSA CONSULTING AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about SANSA CONSULTING AS

Who owns SANSA CONSULTING AS?

ASISA INVEST AS is the largest registered owner, with 100.0%.

What is the revenue of SANSA CONSULTING AS?

SANSA CONSULTING AS had revenue of NOK 161,000 in 2025.

Who is the general manager of SANSA CONSULTING AS?

Amarjit Singh Marjara is registered as general manager of SANSA CONSULTING AS.

Where is SANSA CONSULTING AS based?

SANSA CONSULTING AS has its business address in Lierskogen.

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.