BIZTRAC BETA
Construction of residential and non-residential buildings

TAME HOLDING AS

Org. no. 919510587 Limited company (AS) Asker Incorporated 2017 Active
Ownership graph ↗
Operating profit NOK −25,000
Equity NOK −1.4m
Incorporated 2017
Share capital NOK 100,000

Signals

2 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−1,4 mill kr).
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−25k kr).

TAME HOLDING AS is registered as a limited company in Asker, Akershus with organisation number 919510587. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 2017. Registered share capital is NOK 100,000, divided into 1000 shares. The company's stated purpose is: “Oppføring av bygg og på forretningsmessig grunnlag drive salg og utleie av fast eiendom. Videre å investere i eiendommer, aksjer og hva hermed står i forbindelse.”.

Key figures · 2024

Operating profit
NOK −25,000
Equity
NOK −1.4m

Financial health · 2024

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

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

Who owns TAME HOLDING AS?

EMIL PAASKE
TAME HOLDING AS
· NOK −25,000 profit

TAME HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does TAME HOLDING AS own?

TAME HOLDING AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about TAME HOLDING AS

Who owns TAME HOLDING AS?

EMIL PAASKE is the largest registered owner, with 100.0%.

Who is the general manager of TAME HOLDING AS?

Emil Paaske is registered as general manager of TAME HOLDING AS.

Where is TAME HOLDING AS based?

TAME HOLDING AS has its business address in Asker.

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.