BIZTRAC BETA
Joinery installation

CARO BYGG 1 AS

Org. no. 936652832 Limited company (AS) Oslo Incorporated 2025 Active
Ownership graph ↗
Revenue 2025 NOK 430,000
Operating profit NOK 16,000
Equity NOK 37,000
Incorporated 2025
Share capital NOK 30,000

Signals

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

CARO BYGG 1 AS is registered as a limited company in Oslo, Oslo with organisation number 936652832. The business is classified under joinery installation (NACE 43.320). 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 snekkerarbeid og annet som naturlig sammenfaller med dette, samt deltakelse i andre selskaper, investeringer og nærliggende virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 430,000 in revenue and NOK 16,000 in operating profit.

Key figures · 2025

Revenue
NOK 430,000
Operating profit
NOK 16,000
Equity
NOK 37,000
Est. value
NOK 69,000

Financial health · 2025

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

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

Who owns CARO BYGG 1 AS?

KAMILA SRAMKOWSKA
CARO BYGG 1 AS
NOK 430,000 rev. · NOK 16,000 profit

CARO BYGG 1 AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about CARO BYGG 1 AS

Who owns CARO BYGG 1 AS?

KAMILA SRAMKOWSKA is the largest registered owner, with 100.0%.

What is the revenue of CARO BYGG 1 AS?

CARO BYGG 1 AS had revenue of NOK 430,000 in 2025.

Who is the general manager of CARO BYGG 1 AS?

Kamila Sramkowska is registered as general manager of CARO BYGG 1 AS.

Where is CARO BYGG 1 AS based?

CARO BYGG 1 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 15.06.2026.

Report a problem

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