biztrac. BETA
COMPANY REGISTER PROFILE
991521003 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Accounting and bookkeeping

TD FELLESTJENESTER AS

Org. no. 991521003 Limited company (AS) Sandefjord Incorporated 2007 Active
Revenue 2025 NOK 12.4m
Operating profit NOK −90,000
Equity NOK 131,000
Incorporated 2007
Share capital NOK 100,000

Signals

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

TD FELLESTJENESTER AS is registered as a limited company in Sandefjord, Vestfold with organisation number 991521003. The business is classified under accounting and bookkeeping (NACE 69.202). The company was incorporated in 2007. Registered share capital is NOK 100,000, divided into 1000 shares. The company's stated purpose is: “Salg av varer og tjenester til leietakere, herunder å fordele og rapportere felleskostnader.”. The most recent filed accounts, for the 2025 financial year, show NOK 12.4m in revenue and NOK −90,000 in operating profit.

Former names: TØDDELSETER AS, TØDDØLSETER AS

Key figures · 2025

Revenue
NOK 12.4m
▼ −8 %
Operating profit
NOK −90,000
▲ +26 %
Equity
NOK 131,000
▼ −0 %
Est. value
NOK 13.1m

Financial health · 2025

Liquidity
1.12
Satisfactory
Current assets ÷ current liabilities
Profitability
-0.3%
Not satisfactory
Return on total assets
Solidity
10.9%
Satisfactory
Equity as a share of total capital

Who owns TD FELLESTJENESTER AS?

TD FELLESTJENESTER AS
NOK 12.4m rev. · NOK −90,000 profit

TD FELLESTJENESTER AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about TD FELLESTJENESTER AS

Who owns TD FELLESTJENESTER AS?

AS THOR DAHL is the largest registered owner, with 100.0%.

What is the revenue of TD FELLESTJENESTER AS?

TD FELLESTJENESTER AS had revenue of NOK 12.4m in 2025.

Where is TD FELLESTJENESTER AS based?

TD FELLESTJENESTER AS has its business address in Sandefjord.

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.