BIZTRAC BETA
COMPANY REGISTER PROFILE
937137389 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 02.09.2026
Construction of residential and non-residential buildings

TOTAL SERVICE CONSULTING AS

Org. no. 937137389 Limited company (AS) Sandefjord Incorporated 2025 Active
Ownership graph ↗
Equity NOK 30,000
Incorporated 2025
Share capital NOK 30,000

Signals

1 flags
  • Nystiftet selskap Selskapet ble stiftet 2025-11-24.

TOTAL SERVICE CONSULTING AS is registered as a limited company in Sandefjord, Vestfold with organisation number 937137389. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 2025. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Oppføring og vedlikehold av bygninger.”.

Key figures · 2025

Equity
NOK 30,000
Est. value
NOK 31,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 TOTAL SERVICE CONSULTING AS?

No shareholders are registered for TOTAL SERVICE CONSULTING AS in open Norwegian sources. Shareholder data exists mainly for limited companies (AS/ASA).

Frequently asked questions about TOTAL SERVICE CONSULTING AS

Where is TOTAL SERVICE CONSULTING AS based?

TOTAL SERVICE CONSULTING AS has its business address in Stokke.

Property

Business address Rugdeveien 1A, 3160 Stokke
Cadastral unit 3907-422/264/0/0
Building Tomannsbolig, vertikal · 1 unit

The address this company is registered at, from the company register and matched against the cadastre. It does not say who owns the property — a company may be a tenant, and the address is often its accountant's. Source: Brønnøysundregistrene and © Kartverket.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 02.09.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.