BIZTRAC BETA
COMPANY REGISTER PROFILE
933469298 ORG. NO. 2024 ACCOUNTS 7 SECTIONS
Active UPDATED 15.06.2026
Construction of residential and non-residential buildings

T&D BYGG AS

Org. no. 933469298 Limited company (AS) Bergen Incorporated 2024 Active
Ownership graph ↗
Revenue 2024 NOK 258,000
Operating profit NOK −1,000
Equity NOK 23,000
Incorporated 2024
Share capital NOK 30,000

Signals

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

T&D BYGG AS is registered as a limited company in Bergen, Vestland with organisation number 933469298. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 2024. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Oppføring av bygninger.”. The most recent filed accounts, for the 2024 financial year, show NOK 258,000 in revenue and NOK −1,000 in operating profit.

Key figures · 2024

Revenue
NOK 258,000
Operating profit
NOK −1,000
Equity
NOK 23,000
Est. value
NOK 100,000

Financial health · 2024

Liquidity
4.82
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
79.3%
Weak
Equity as a share of total capital

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

Who owns T&D BYGG AS?

TONEL CALOIAN
T&D BYGG AS
NOK 258,000 rev. · NOK −1,000 profit

T&D BYGG AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about T&D BYGG AS

Who owns T&D BYGG AS?

TONEL CALOIAN is the largest registered owner, with 100.0%.

What is the revenue of T&D BYGG AS?

T&D BYGG AS had revenue of NOK 258,000 in 2024.

Who is the general manager of T&D BYGG AS?

Tonel Caloian is registered as general manager of T&D BYGG AS.

Where is T&D BYGG AS based?

T&D BYGG AS has its business address in Bergen.

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.