BIZTRAC BETA
COMPANY REGISTER PROFILE
928991016 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 02.09.2026
Uoppgitt

TANG OG TARE AS

Org. no. 928991016 Limited company (AS) Stavanger Incorporated 2022 Active
Ownership graph ↗
Equity NOK −486,000
Incorporated 2022
Share capital NOK 30,000

Signals

1 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−486k kr).

TANG OG TARE AS is registered as a limited company in Stavanger, Rogaland with organisation number 928991016. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2022. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Aksjeinvestering.”.

Key figures · 2025

Equity
NOK −486,000
▲ +1 %

Financial health · 2025

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

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

Who owns TANG OG TARE AS?

TANG OG TARE AS

TANG OG TARE AS has 1 registered shareholder:

All shareholders and roles →

Which companies does TANG OG TARE AS own?

TANG OG TARE AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about TANG OG TARE AS

Who owns TANG OG TARE AS?

Jon Vikse is the largest registered owner, with 100.0%.

Where is TANG OG TARE AS based?

TANG OG TARE AS has its business address in Stavanger.

Property

Business address Fjellfaret 5A, 4025 Stavanger
Cadastral unit 1103-29/1072/0/0
Building Enebolig m/hybel/sokkelleil. · 2 units

The address this company is registered at, from the company register and matched against the cadastre. It does not say who owns the property — a company may be a tenant, and the address is often its accountant's. Source: Brønnøysundregistrene and © Kartverket.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 02.09.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.