BIZTRAC BETA
Rental and leasing of cars and light motor vehicles

KROKEN VAREBIL AS

Org. no. 933153916 Limited company (AS) Bergen Incorporated 2024 Active
Ownership graph ↗
Revenue 2025 NOK 1.2m
Operating profit NOK 91,000
Equity NOK 106,000
Incorporated 2024
Share capital NOK 30,000

KROKEN VAREBIL AS is registered as a limited company in Bergen, Vestland with organisation number 933153916. The business is classified under rental and leasing of cars and light motor vehicles (NACE 77.110). The company was incorporated in 2024. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Selge varer og tjenester innen utleie av personbiler 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 1.2m in revenue and NOK 91,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.2m
Operating profit
NOK 91,000
Equity
NOK 106,000
Est. value
NOK 305,000

Financial health · 2025

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

Who owns KROKEN VAREBIL AS?

STRANDVIK BUTIKKDRIFT HOLDING AS
KROKEN VAREBIL AS
NOK 1.2m rev. · NOK 91,000 profit

KROKEN VAREBIL AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about KROKEN VAREBIL AS

Who owns KROKEN VAREBIL AS?

STRANDVIK BUTIKKDRIFT HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of KROKEN VAREBIL AS?

KROKEN VAREBIL AS had revenue of NOK 1.2m in 2025.

Who is the general manager of KROKEN VAREBIL AS?

Frode Tvedt is registered as general manager of KROKEN VAREBIL AS.

Where is KROKEN VAREBIL AS based?

KROKEN VAREBIL AS has its business address in Fyllingsdalen.

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.