BIZTRAC BETA
Business and other management consultancy activities

SINGA AS

Org. no. 918027343 Limited company (AS) Sigdal Incorporated 2016 Active
Ownership graph ↗
Revenue 2025 NOK 259,000
Operating profit NOK −350,000
Equity NOK 443,000
Incorporated 2016
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−350k kr).

SINGA AS is registered as a limited company in Sigdal, Buskerud with organisation number 918027343. The business is classified under business and other management consultancy activities (NACE 70.200). The company was incorporated in 2016. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Rådgivning og konsulentvirksomhet, samt deltakelse i andre selskaper.”. The most recent filed accounts, for the 2025 financial year, show NOK 259,000 in revenue and NOK −350,000 in operating profit.

Key figures · 2025

Revenue
NOK 259,000
Operating profit
NOK −350,000
Equity
NOK 443,000
Est. value
NOK 488,000

Financial health · 2025

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

Who owns SINGA AS?

PER ARNE LISLIEN
SINGA AS
NOK 259,000 rev. · NOK −350,000 profit

SINGA AS has 2 registered shareholders:

All shareholders and roles →

Which companies does SINGA AS own?

SINGA AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about SINGA AS

Who owns SINGA AS?

PER ARNE LISLIEN is the largest registered owner, with 50.0%.

What is the revenue of SINGA AS?

SINGA AS had revenue of NOK 259,000 in 2025.

Who is the general manager of SINGA AS?

Ellen Anne Svartbrenna Bye is registered as general manager of SINGA AS.

Where is SINGA AS based?

SINGA AS has its business address in Nedre Eggedal.

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.