biztrac. BETA
COMPANY REGISTER PROFILE
989589164 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Computer programming activities

TALL HOLDING AS

Org. no. 989589164 Limited company (AS) Porsgrunn Incorporated 2006 Active
Revenue 2025 NOK 0
Operating profit NOK −118,000
Equity NOK 2.5m
Incorporated 2006
Share capital NOK 100,000

Signals

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

TALL HOLDING AS is registered as a limited company in Porsgrunn, Telemark with organisation number 989589164. The business is classified under computer programming activities (NACE 62.100). The company was incorporated in 2006. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Investering i aksjer, fast eiendom samt helt eller delvis å delta i eller eie andre selskap.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −118,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −118,000
▲ +23 %
Equity
NOK 2.5m
▼ −0 %
Est. value
NOK 4.5m

Financial health · 2025

Liquidity
–
Not available
Current assets ÷ current liabilities
Profitability
-0.5%
Not satisfactory
Return on total assets
Solidity
83.2%
Very good
Equity as a share of total capital

Who owns TALL HOLDING AS?

TALL HOLDING AS
NOK 0 rev. · NOK −118,000 profit

TALL HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about TALL HOLDING AS

Who owns TALL HOLDING AS?

Lena Charlotte Talleivsen is the largest registered owner, with 100.0%.

What is the revenue of TALL HOLDING AS?

TALL HOLDING AS had revenue of NOK 0 in 2025.

Who is the general manager of TALL HOLDING AS?

Lena Charlotte Talleivsen is registered as general manager of TALL HOLDING AS.

Where is TALL HOLDING AS based?

TALL HOLDING AS has its business address in Porsgrunn.

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

Report a problem

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