BIZTRAC BETA
Roofing activities

JB TAK AS

Org. no. 936649777 Limited company (AS) Trondheim Incorporated 2025 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −7,000
Equity NOK 23,000
Incorporated 2025
Share capital NOK 30,000

Signals

2 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−7k kr).
  • Nystiftet selskap Selskapet ble stiftet 2025-10-28.

JB TAK AS is registered as a limited company in Trondheim, Trøndelag with organisation number 936649777. The business is classified under roofing activities (NACE 43.410). The company was incorporated in 2025. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Utføre isoleringsarbeid, taktekking og membrantekking, samt annen virksomhet som naturlig hører sammen med dette. Selskapet kan også investere i og erverve aksjer eller andeler i andre selskaper.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −7,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −7,000
Equity
NOK 23,000
Est. value
NOK 24,000

Financial health · 2025

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

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

Who owns JB TAK AS?

EMCM AS
JB TAK AS
NOK 0 rev. · NOK −7,000 profit

JB TAK AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about JB TAK AS

Who owns JB TAK AS?

EMCM AS is the largest registered owner, with 100.0%.

What is the revenue of JB TAK AS?

JB TAK AS had revenue of NOK 0 in 2025.

Who is the general manager of JB TAK AS?

Cassandra Jensen Brobakk is registered as general manager of JB TAK AS.

Where is JB TAK AS based?

JB TAK AS has its business address in Saupstad.

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.