BIZTRAC BETA
COMPANY REGISTER PROFILE
935826861 ORG. NO. 7 SECTIONS
Active UPDATED 02.09.2026
Rental and operating of own or leased real estate

KEBRO HOLDING AS

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

Signals

1 flags
  • Mangler regnskap Ingen årsregnskap er registrert for selskapet.

KEBRO HOLDING AS is registered as a limited company in Sandnes, Rogaland with organisation number 935826861. 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 30000 shares. The company's stated purpose is: “Investere i selskaper og eiendom og alt annet som naturlig faller sammen med dette, herunder å delta i andre selskaper med lignende virksomhet, kjøp og salg av aksjer, eller på annen måte gjøre seg interessert i andre foretagende.”.

Who owns KEBRO HOLDING AS?

KEBRO HOLDING AS

KEBRO HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about KEBRO HOLDING AS

Who owns KEBRO HOLDING AS?

KEVIN ROVIK is the largest registered owner, with 100.0%.

Who is the general manager of KEBRO HOLDING AS?

Kevin Rovik is registered as general manager of KEBRO HOLDING AS.

Where is KEBRO HOLDING AS based?

KEBRO HOLDING AS has its business address in Sandnes.

Property

Business address Karen Grude Kohts plass 3B, 4306 Sandnes
Cadastral unit 1108-111/1286/0/0
Building Stort frittliggende boligbygg på 5 etg el mer · 73 units

4 companies are registered at this address.

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.