BIZTRAC BETA
Construction of residential and non-residential buildings

BYGGMESTER A K BRAUT AS

Org. no. 992510315 Limited company (AS) Klepp Incorporated 2008 Active
Ownership graph ↗
Revenue 2025 NOK 1.4m
Operating profit NOK 62,000
Equity NOK 558,000
Incorporated 2008
Share capital NOK 100,000

BYGGMESTER A K BRAUT AS is registered as a limited company in Klepp, Rogaland with organisation number 992510315. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 2008. Registered share capital is NOK 100,000, divided into 10000 shares. The company's stated purpose is: “Byggmesteroppdrag innen byggebransjen, samt deltagelse i andre foretak med lignende virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.4m in revenue and NOK 62,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.4m
Operating profit
NOK 62,000
Equity
NOK 558,000
Est. value
NOK 526,000

Financial health · 2025

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

Who owns BYGGMESTER A K BRAUT AS?

ARNE KENNETH BRAUT
BYGGMESTER A K BRAUT AS
NOK 1.4m rev. · NOK 62,000 profit

BYGGMESTER A K BRAUT AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about BYGGMESTER A K BRAUT AS

Who owns BYGGMESTER A K BRAUT AS?

ARNE KENNETH BRAUT is the largest registered owner, with 100.0%.

What is the revenue of BYGGMESTER A K BRAUT AS?

BYGGMESTER A K BRAUT AS had revenue of NOK 1.4m in 2025.

Who is the general manager of BYGGMESTER A K BRAUT AS?

Arne Kenneth Braut is registered as general manager of BYGGMESTER A K BRAUT AS.

Where is BYGGMESTER A K BRAUT AS based?

BYGGMESTER A K BRAUT AS has its business address in Kvernaland.

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.