biztrac. BETA
COMPANY REGISTER PROFILE
935481953 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Traditional, complementary and alternative medicine activities

KIROPRAKTOR JACOB STANG AS

Org. no. 935481953 Limited company (AS) Oslo Incorporated 2025 Active
Operating profit NOK −700
Equity NOK 29,000
Incorporated 2025
Share capital NOK 30,000

Signals

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

KIROPRAKTOR JACOB STANG AS is registered as a limited company in Oslo, Oslo with organisation number 935481953. The business is classified under traditional, complementary and alternative medicine activities (NACE 86.960). The company was incorporated in 2025. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Selge varer og tjenester innen kiropraktorarbeid og annet som naturlig sammenfaller med dette, samt deltakelse i andre selskaper, investeringer og nærliggende virksomhet.”.

Key figures · 2025

Operating profit
NOK −700
Equity
NOK 29,000
Est. value
NOK 45,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 KIROPRAKTOR JACOB STANG AS?

KIROPRAKTOR JACOB STANG AS
· NOK −700 profit

KIROPRAKTOR JACOB STANG AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about KIROPRAKTOR JACOB STANG AS

Who owns KIROPRAKTOR JACOB STANG AS?

Jacob Stang is the largest registered owner, with 100.0%.

Who is the general manager of KIROPRAKTOR JACOB STANG AS?

Jacob Stang is registered as general manager of KIROPRAKTOR JACOB STANG AS.

Where is KIROPRAKTOR JACOB STANG AS based?

KIROPRAKTOR JACOB STANG AS has its business address in Oslo.

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.