BIZTRAC BETA
Rental and operating of own or leased real estate

BRØDRENE VIKSE AS

Org. no. 997034740 Limited company (AS) Karmøy Incorporated 2011 Active
Ownership graph ↗
Revenue 2024 NOK 412,000
Operating profit NOK 369,000
Equity NOK 386,000
Incorporated 2011
Share capital NOK 100,000

BRØDRENE VIKSE AS is registered as a limited company in Karmøy, Rogaland with organisation number 997034740. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2011. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Kjøp, salg og utleie av fast eiendom. Videre kan selskapet drive utleie av maskiner og utstyr med tilhørende tjenester. Selskapet kan delta i supplerende eller lignende virksomheter ved aksjetegning eller på annen måte. Plastring av glassfiberkonstruksjoner samt kjøp og salg av brukte fritidsbåter.”. The most recent filed accounts, for the 2024 financial year, show NOK 412,000 in revenue and NOK 369,000 in operating profit.

Key figures · 2024

Revenue
NOK 412,000
Operating profit
NOK 369,000
Equity
NOK 386,000
Est. value
NOK 859,000

Financial health · 2024

Liquidity
0.10
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
12.1%
Satisfactory
Equity as a share of total capital

Who owns BRØDRENE VIKSE AS?

MIKAEL FRAMNES VIKSE
BRØDRENE VIKSE AS
NOK 412,000 rev. · NOK 369,000 profit

BRØDRENE VIKSE AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about BRØDRENE VIKSE AS

Who owns BRØDRENE VIKSE AS?

MIKAEL FRAMNES VIKSE is the largest registered owner, with 75.0%.

What is the revenue of BRØDRENE VIKSE AS?

BRØDRENE VIKSE AS had revenue of NOK 412,000 in 2024.

Where is BRØDRENE VIKSE AS based?

BRØDRENE VIKSE AS has its business address in Kvalavåg.

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.