BIZTRAC BETA
Computer consultancy and computer facilities management activities

TINGR AS

Org. no. 892071322 Limited company (AS) Bergen Incorporated 2007 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −13,000
Equity NOK −330,000
Incorporated 2007
Share capital NOK 180,000

Signals

2 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−330k kr).
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−13k kr).

TINGR AS is registered as a limited company in Bergen, Vestland with organisation number 892071322. The business is classified under computer consultancy and computer facilities management activities (NACE 62.200). The company was incorporated in 2007. Registered share capital is NOK 180,000, divided into 450000 shares. The company's stated purpose is: “Tilby løsninger for korrekt avstemming for ethvert område for valg og avgjørelser.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −13,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −13,000
Equity
NOK −330,000

Financial health · 2025

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

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

Who owns TINGR AS?

CITIUS DATA AS
TINGR AS
NOK 0 rev. · NOK −13,000 profit

TINGR AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about TINGR AS

Who owns TINGR AS?

CITIUS DATA AS is the largest registered owner, with 100.0%.

What is the revenue of TINGR AS?

TINGR AS had revenue of NOK 0 in 2025.

Who is the general manager of TINGR AS?

Jon Anders Tjugen is registered as general manager of TINGR AS.

Where is TINGR AS based?

TINGR AS has its business address in Søreidgrend.

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.