BIZTRAC BETA
Computer consultancy and computer facilities management activities

SIGNNATIV AS

Org. no. 836570642 Limited company (AS) Ringsaker Incorporated 2025 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −3,000
Equity NOK 29,000
Incorporated 2025
Share capital NOK 40,000

Signals

2 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−3k kr).
  • Nystiftet selskap Selskapet ble stiftet 2025-11-10.

SIGNNATIV AS is registered as a limited company in Ringsaker, Innlandet with organisation number 836570642. The business is classified under computer consultancy and computer facilities management activities (NACE 62.200). The company was incorporated in 2025. Registered share capital is NOK 40,000, divided into 40000 shares. The company's stated purpose is: “Å utvikle, drifte og selge nettsider, digitale løsninger og AI-algoritmer, samt investering og annen virksomhet som står i naturlig sammenheng med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −3,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −3,000
Equity
NOK 29,000
Est. value
NOK 53,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 SIGNNATIV AS?

BJØRN STEEN
SIGNNATIV AS
NOK 0 rev. · NOK −3,000 profit

SIGNNATIV AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about SIGNNATIV AS

Who owns SIGNNATIV AS?

BJØRN STEEN is the largest registered owner, with 100.0%.

What is the revenue of SIGNNATIV AS?

SIGNNATIV AS had revenue of NOK 0 in 2025.

Where is SIGNNATIV AS based?

SIGNNATIV AS has its business address in Brumunddal.

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.