BIZTRAC BETA
Activities of agents involved in the wholesale of textiles, clothing, fur, footwear and leather goods

TEKO ATTIVO AS

Org. no. 919710829 Limited company (AS) Oslo Incorporated 2017 Active
Ownership graph ↗
Revenue 2024 NOK 5.6m
Operating profit NOK 1.3m
Equity NOK −5.4m
Incorporated 2017
Share capital NOK 30,000

Signals

1 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−5,4 mill kr).

TEKO ATTIVO AS is registered as a limited company in Oslo, Oslo with organisation number 919710829. The business is classified under activities of agents involved in the wholesale of textiles, clothing, fur, footwear and leather goods (NACE 46.160). The company was incorporated in 2017. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Agentur og detaljhandel av klær, tekstiler og relaterte produkter, samt deltagelse i virksomhet som naturlig følger av driften.”. The most recent filed accounts, for the 2024 financial year, show NOK 5.6m in revenue and NOK 1.3m in operating profit.

Key figures · 2024

Revenue
NOK 5.6m
Operating profit
NOK 1.3m
Equity
NOK −5.4m
Est. value
NOK 6.6m

Financial health · 2024

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

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

Who owns TEKO ATTIVO AS?

IDEAL FINANS AS
TEKO ATTIVO AS
NOK 5.6m rev. · NOK 1.3m profit

TEKO ATTIVO AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about TEKO ATTIVO AS

Who owns TEKO ATTIVO AS?

IDEAL FINANS AS is the largest registered owner, with 100.0%.

What is the revenue of TEKO ATTIVO AS?

TEKO ATTIVO AS had revenue of NOK 5.6m in 2024.

Where is TEKO ATTIVO AS based?

TEKO ATTIVO AS has its business address in Oslo.

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.