biztrac. BETA
COMPANY REGISTER PROFILE
922169861 ORG. NO. 2025 ACCOUNTS 9 SECTIONS
Active UPDATED 03.10.2026
Construction of residential and non-residential buildings

BYKLE BYGG AS

Org. no. 922169861 Limited company (AS) Bykle Incorporated 2019 Active
Ownership graph ↗
Revenue 2025 NOK 11.2m
Operating profit NOK 1.7m
Equity NOK 7.9m
Incorporated 2019
Share capital NOK 100,000

BYKLE BYGG AS is registered as a limited company in Bykle, Agder with organisation number 922169861. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 2019. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Oppføring og vedlikehold av bygg og anlegg. Videre enhver virksomhet som lar seg kombinere med dette. Selskapet skal også kunne delta i andre selskaper.”. The most recent filed accounts, for the 2025 financial year, show NOK 11.2m in revenue and NOK 1.7m in operating profit.

Key figures · 2025

Revenue
NOK 11.2m
▼ −12 %
Operating profit
NOK 1.7m
▼ −32 %
Equity
NOK 7.9m
▲ +8 %
Est. value
NOK 9.6m

Financial health · 2025

Liquidity
4.22
Very good
Current assets ÷ current liabilities
Profitability
17.4%
Very good
Return on total assets
Solidity
78.2%
Very good
Equity as a share of total capital

Who owns BYKLE BYGG AS?

BYKLE BYGG AS
NOK 11.2m rev. · NOK 1.7m profit

BYKLE BYGG AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about BYKLE BYGG AS

Who owns BYKLE BYGG AS?

CARMA INVEST AS is the largest registered owner, with 50.0%.

What is the revenue of BYKLE BYGG AS?

BYKLE BYGG AS had revenue of NOK 11.2m in 2025.

Who is the general manager of BYKLE BYGG AS?

Ola Birger K Trydal is registered as general manager of BYKLE BYGG AS.

Where is BYKLE BYGG AS based?

BYKLE BYGG AS has its business address in Bykle.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.