BIZTRAC BETA
Research and experimental development on natural sciences and engineering

SICHER SENSE AS

Org. no. 928167526 Limited company (AS) Gjøvik Incorporated 2021 Active
Ownership graph ↗
Revenue 2025 NOK 1,000
Operating profit NOK −7,000
Equity NOK 78
Incorporated 2021
Share capital NOK 30,000

Signals

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

SICHER SENSE AS is registered as a limited company in Gjøvik, Innlandet with organisation number 928167526. The business is classified under research and experimental development on natural sciences and engineering (NACE 72.100). The company was incorporated in 2021. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Utvikle og selge produkter og tjenester innen miljøvennlig transport.”. The most recent filed accounts, for the 2025 financial year, show NOK 1,000 in revenue and NOK −7,000 in operating profit.

Key figures · 2025

Revenue
NOK 1,000
Operating profit
NOK −7,000
Equity
NOK 78
Est. value
NOK 1,000

Financial health · 2025

Liquidity
Not available
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
100.0%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns SICHER SENSE AS?

BIAN YANG
SICHER SENSE AS
NOK 1,000 rev. · NOK −7,000 profit

SICHER SENSE AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about SICHER SENSE AS

Who owns SICHER SENSE AS?

BIAN YANG is the largest registered owner, with 60.0%.

What is the revenue of SICHER SENSE AS?

SICHER SENSE AS had revenue of NOK 1,000 in 2025.

Who is the general manager of SICHER SENSE AS?

Bian Yang is registered as general manager of SICHER SENSE AS.

Where is SICHER SENSE AS based?

SICHER SENSE AS has its business address in Gjøvik.

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.