biztrac. BETA
COMPANY REGISTER PROFILE
925817465 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Uoppgitt

TALLGLEDE HOLDING AS

Org. no. 925817465 Limited company (AS) Asker Incorporated 2020 Active
Revenue 2025 NOK 200,000
Operating profit NOK 200,000
Equity NOK 116,000
Incorporated 2020
Share capital NOK 30,000

TALLGLEDE HOLDING AS is registered as a limited company in Asker, Akershus with organisation number 925817465. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2020. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Investering og deltagelse i andre selskaper og andre produkter/tjenester som naturlig hører sammen med dette, herunder å delta i andre selskap med lignende virksomhet, og kjøp og salg av aksjer eller på annen måte gjøre seg interessert i andre foretak.”. The most recent filed accounts, for the 2025 financial year, show NOK 200,000 in revenue and NOK 200,000 in operating profit.

Former names: HANDYMAN 4U AS

Key figures · 2025

Revenue
NOK 200,000
Operating profit
NOK 200,000
▲ +30266 %
Equity
NOK 116,000
▲ +5378 %
Est. value
NOK 340,000

Financial health · 2025

Liquidity
1.63
Good
Current assets ÷ current liabilities
Profitability
–
Not available
Return on total assets
Solidity
38.7%
Good
Equity as a share of total capital

Who owns TALLGLEDE HOLDING AS?

TALLGLEDE HOLDING AS
NOK 200,000 rev. · NOK 200,000 profit

TALLGLEDE HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about TALLGLEDE HOLDING AS

Who owns TALLGLEDE HOLDING AS?

Børge Thue is the largest registered owner, with 100.0%.

What is the revenue of TALLGLEDE HOLDING AS?

TALLGLEDE HOLDING AS had revenue of NOK 200,000 in 2025.

Where is TALLGLEDE HOLDING AS based?

TALLGLEDE 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 03.10.2026.

Report a problem

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