biztrac. BETA
COMPANY REGISTER PROFILE
816696062 ORG. NO. 2025 ACCOUNTS 9 SECTIONS
Active UPDATED 03.10.2026
Plumbing installation

JT HOLDING AS

Org. no. 816696062 Limited company (AS) Namsos Incorporated 2016 Active
Ownership graph ↗
Operating profit NOK −17,000
Equity NOK 2.1m
Incorporated 2016
Share capital NOK 175,000

Signals

2 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−17k kr).
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

JT HOLDING AS is registered as a limited company in Namsos, Trøndelag with organisation number 816696062. The business is classified under plumbing installation (NACE 43.221). The company was incorporated in 2016. Registered share capital is NOK 175,000, divided into 175 shares. The company's stated purpose is: “Investeringer i andre selskaper, herunder eie og forvalte askjer, samt det naturlige som står i forbindelse med dette.”.

Former names: J.NILSEN VVS AS

Key figures · 2025

Operating profit
NOK −17,000
▼ −33 %
Equity
NOK 2.1m
▼ −1 %
Est. value
NOK 3.7m

Financial health · 2025

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

Who owns JT HOLDING AS?

JT HOLDING AS
· NOK −17,000 profit

JT HOLDING AS has 2 registered shareholders:

All shareholders and roles →

Which companies does JT HOLDING AS own?

JT HOLDING AS holds stakes in 3 companies:

See the full ownership structure →

Frequently asked questions about JT HOLDING AS

Who owns JT HOLDING AS?

Joakim Nilsen is the largest registered owner, with 71.4%.

Who is the general manager of JT HOLDING AS?

Joakim Nilsen is registered as general manager of JT HOLDING AS.

Where is JT HOLDING AS based?

JT HOLDING AS has its business address in Namsos.

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.