BIZTRAC BETA
Roofing activities

TAKFORNYER'N AS

Org. no. 921517025 Limited company (AS) Sandefjord Incorporated 2018 Active
Ownership graph ↗
Revenue 2025 NOK 4.1m
Operating profit NOK 418,000
Equity NOK −123,000
Incorporated 2018
Share capital NOK 30,000

Signals

1 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−123k kr).

TAKFORNYER'N AS is registered as a limited company in Sandefjord, Vestfold with organisation number 921517025. The business is classified under roofing activities (NACE 43.410). The company was incorporated in 2018. Registered share capital is NOK 30,000, divided into 6 shares. The company's stated purpose is: “Vask, impregnering og sprøytemaling av takstein, samt utføring av diverse malertjenester og vedlikeholdstjenester.”. The most recent filed accounts, for the 2025 financial year, show NOK 4.1m in revenue and NOK 418,000 in operating profit.

Key figures · 2025

Revenue
NOK 4.1m
Operating profit
NOK 418,000
Equity
NOK −123,000
Est. value
NOK 2.5m

Financial health · 2025

Liquidity
0.68
Weak
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-22.8%
Weak
Equity as a share of total capital

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

Who owns TAKFORNYER'N AS?

IMAD AHMED BADR ALZUBAIDI
TAKFORNYER'N AS
NOK 4.1m rev. · NOK 418,000 profit

TAKFORNYER'N AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about TAKFORNYER'N AS

Who owns TAKFORNYER'N AS?

IMAD AHMED BADR ALZUBAIDI is the largest registered owner, with 100.0%.

What is the revenue of TAKFORNYER'N AS?

TAKFORNYER'N AS had revenue of NOK 4.1m in 2025.

Who is the general manager of TAKFORNYER'N AS?

Imad Ahmed Badr Alzubaidi is registered as general manager of TAKFORNYER'N AS.

Where is TAKFORNYER'N AS based?

TAKFORNYER'N AS has its business address in Stokke.

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.