biztrac. BETA
COMPANY REGISTER PROFILE
936147712 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Intermediation service activities for real estate activities

TAKSTSAMVIRKE AS

Org. no. 936147712 Limited company (AS) Sarpsborg Incorporated 2025 Active
Revenue 2025 NOK 0
Operating profit NOK −18,000
Equity NOK 5,000
Incorporated 2025
Share capital NOK 30,000

Signals

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

TAKSTSAMVIRKE AS is registered as a limited company in Sarpsborg, Østfold with organisation number 936147712. The business is classified under intermediation service activities for real estate activities (NACE 68.310). The company was incorporated in 2025. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Taksering, rådgivende ingeniørtjenester og konsulentbistand innen fast eiendom eller formidling av dette samt annen virksomhet som kan tjene eiernes interesser.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −18,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −18,000
Equity
NOK 5,000
Est. value
NOK 5,000

Financial health · 2025

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

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

Who owns TAKSTSAMVIRKE AS?

TAKSTSAMVIRKE AS has 4 registered shareholders:

All shareholders and roles →

Frequently asked questions about TAKSTSAMVIRKE AS

Who owns TAKSTSAMVIRKE AS?

Marcus Pettersen is the largest registered owner, with 25.0%.

What is the revenue of TAKSTSAMVIRKE AS?

TAKSTSAMVIRKE AS had revenue of NOK 0 in 2025.

Where is TAKSTSAMVIRKE AS based?

TAKSTSAMVIRKE AS has its business address in Skjeberg.

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.