BIZTRAC BETA
Rental and operating of own or leased real estate

BYGDEVEIEN 24 AS

Org. no. 995641291 Limited company (AS) Kvæfjord Incorporated 2010 Active
Ownership graph ↗
Revenue 2025 NOK 2.0m
Operating profit NOK 1.6m
Equity NOK 4.9m
Incorporated 2010
Share capital NOK 2.0m

Signals

1 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

BYGDEVEIEN 24 AS is registered as a limited company in Kvæfjord, Troms with organisation number 995641291. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2010. Registered share capital is NOK 2.0m, divided into 2000 shares. The company's stated purpose is: “Utvikling og utleie av fast eiendom samt virksomhet som står i forbindelse med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 2.0m in revenue and NOK 1.6m in operating profit.

Key figures · 2025

Revenue
NOK 2.0m
Operating profit
NOK 1.6m
Equity
NOK 4.9m
Est. value
NOK 6.6m

Financial health · 2025

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

Who owns BYGDEVEIEN 24 AS?

COOP NORD SA
BYGDEVEIEN 24 AS
NOK 2.0m rev. · NOK 1.6m profit

BYGDEVEIEN 24 AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about BYGDEVEIEN 24 AS

Who owns BYGDEVEIEN 24 AS?

COOP NORD SA is the largest registered owner, with 100.0%.

What is the revenue of BYGDEVEIEN 24 AS?

BYGDEVEIEN 24 AS had revenue of NOK 2.0m in 2025.

Who is the general manager of BYGDEVEIEN 24 AS?

Pål Kristian Wilhelmsen is registered as general manager of BYGDEVEIEN 24 AS.

Where is BYGDEVEIEN 24 AS based?

BYGDEVEIEN 24 AS has its business address in Borkenes.

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.