biztrac. BETA
COMPANY REGISTER PROFILE
936910211 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Rental and operating of own or leased real estate

KRITTVEIEN 135 AS

Org. no. 936910211 Limited company (AS) Kristiansand Incorporated 2025 Active
Equity NOK 20,000
Incorporated 2025
Share capital NOK 30,000

Signals

1 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

KRITTVEIEN 135 AS is registered as a limited company in Kristiansand, Agder with organisation number 936910211. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2025. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Utvikling av eiendom, oppføring av næringsbygg og arbeid knyttet til bygg og anlegg, samt utleie av eiendom. Kjøp og salg av aksjer, kjøp og salg av eiendom herunder delta i andre selskap med tilsvarende virksomhet. Deltakelse i andre selskap med virksomhet som er knyttet til eiendom.”.

Key figures · 2025

Equity
NOK 20,000
Est. value
NOK 18,000

Financial health · 2025

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

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

Who owns KRITTVEIEN 135 AS?

KRITTVEIEN 135 AS

KRITTVEIEN 135 AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about KRITTVEIEN 135 AS

Who owns KRITTVEIEN 135 AS?

MBI AS is the largest registered owner, with 100.0%.

Who is the general manager of KRITTVEIEN 135 AS?

Øystein Marken is registered as general manager of KRITTVEIEN 135 AS.

Where is KRITTVEIEN 135 AS based?

KRITTVEIEN 135 AS has its business address in Kristiansand S.

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.