BIZTRAC BETA
Construction of residential and non-residential buildings

BYGGMESTER KROKEIDE AS

Org. no. 931430807 Limited company (AS) Øygarden Incorporated 2023 Active
Ownership graph ↗
Revenue 2024 NOK 1.2m
Operating profit NOK 32,000
Equity NOK 48,000
Incorporated 2023
Share capital NOK 30,000

BYGGMESTER KROKEIDE AS is registered as a limited company in Øygarden, Vestland with organisation number 931430807. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 2023. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Tømrer og innredningsarbeider for private og næringslivet.”. The most recent filed accounts, for the 2024 financial year, show NOK 1.2m in revenue and NOK 32,000 in operating profit.

Key figures · 2024

Revenue
NOK 1.2m
Operating profit
NOK 32,000
Equity
NOK 48,000
Est. value
NOK 127,000

Financial health · 2024

Liquidity
0.91
Weak
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
11.8%
Weak
Equity as a share of total capital

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

Who owns BYGGMESTER KROKEIDE AS?

FRODE HOPLAND KROKEIDE
BYGGMESTER KROKEIDE AS
NOK 1.2m rev. · NOK 32,000 profit

BYGGMESTER KROKEIDE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about BYGGMESTER KROKEIDE AS

Who owns BYGGMESTER KROKEIDE AS?

FRODE HOPLAND KROKEIDE is the largest registered owner, with 100.0%.

What is the revenue of BYGGMESTER KROKEIDE AS?

BYGGMESTER KROKEIDE AS had revenue of NOK 1.2m in 2024.

Who is the general manager of BYGGMESTER KROKEIDE AS?

Frode Hopland Krokeide is registered as general manager of BYGGMESTER KROKEIDE AS.

Where is BYGGMESTER KROKEIDE AS based?

BYGGMESTER KROKEIDE AS has its business address in Kolltveit.

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.