BIZTRAC BETA
Civil engineering activities

TØMRERMESTER TORP AS

Org. no. 935631866 Limited company (AS) Nordre Follo Incorporated 2025 Active
Ownership graph ↗
Revenue 2025 NOK 151,000
Operating profit NOK −23,000
Equity NOK 688
Incorporated 2025
Share capital NOK 30,000

Signals

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

TØMRERMESTER TORP AS is registered as a limited company in Nordre Follo, Akershus with organisation number 935631866. The business is classified under civil engineering activities (NACE 71.121). The company was incorporated in 2025. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Taksering, byggeledelse og byggeprosjekter.”. The most recent filed accounts, for the 2025 financial year, show NOK 151,000 in revenue and NOK −23,000 in operating profit.

Key figures · 2025

Revenue
NOK 151,000
Operating profit
NOK −23,000
Equity
NOK 688
Est. value
NOK 159,000

Financial health · 2025

Liquidity
1.00
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
0.5%
Weak
Equity as a share of total capital

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

Who owns TØMRERMESTER TORP AS?

STÅLE TORP
TØMRERMESTER TORP AS
NOK 151,000 rev. · NOK −23,000 profit

TØMRERMESTER TORP AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about TØMRERMESTER TORP AS

Who owns TØMRERMESTER TORP AS?

STÅLE TORP is the largest registered owner, with 60.0%.

What is the revenue of TØMRERMESTER TORP AS?

TØMRERMESTER TORP AS had revenue of NOK 151,000 in 2025.

Who is the general manager of TØMRERMESTER TORP AS?

Ståle Torp is registered as general manager of TØMRERMESTER TORP AS.

Where is TØMRERMESTER TORP AS based?

TØMRERMESTER TORP AS has its business address in Kråkstad.

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.