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

TATANKA AS

Org. no. 990985138 Limited company (AS) Oslo Incorporated 2007 Active
Ownership graph ↗
Operating profit NOK −4,000
Equity NOK 1.4m
Incorporated 2007
Share capital NOK 110,000

Signals

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

TATANKA AS is registered as a limited company in Oslo, Oslo with organisation number 990985138. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2007. Registered share capital is NOK 110,000, divided into 11000 shares. The company's stated purpose is: “Kjøp og salg av verdipapirer og virksomhet i tilknytning til dette.”.

Key figures · 2025

Operating profit
NOK −4,000
▲ +27 %
Equity
NOK 1.4m
▼ −2 %
Est. value
NOK 2.2m

Financial health · 2025

Liquidity
4.66
Very good
Current assets ÷ current liabilities
Profitability
23.9%
Very good
Return on total assets
Solidity
84.6%
Very good
Equity as a share of total capital

Who owns TATANKA AS?

TATANKA AS
· NOK −4,000 profit

TATANKA AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about TATANKA AS

Who owns TATANKA AS?

RUNAR STRAND is the largest registered owner, with 100.0%.

Who is the general manager of TATANKA AS?

Runar Strand is registered as general manager of TATANKA AS.

Where is TATANKA AS based?

TATANKA AS has its business address in Oslo.

Property

Business address Nordbergveien 42, 0875 Oslo
Cadastral unit 301-52/1/0/0
Building Enebolig · 1 unit

8 companies are registered at this address.

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.