BIZTRAC BETA
COMPANY REGISTER PROFILE
982312337 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 15.06.2026
Construction of residential and non-residential buildings

BOLIG BYGG ÅLESUND AS

Org. no. 982312337 Limited company (AS) Giske Incorporated 2000 Active
Ownership graph ↗
Operating profit NOK −3,000
Equity NOK −1.3m
Incorporated 2000
Share capital NOK 140,000

Signals

2 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−1,3 mill kr).
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−3k kr).

BOLIG BYGG ÅLESUND AS is registered as a limited company in Giske, Møre og Romsdal with organisation number 982312337. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 2000. Registered share capital is NOK 140,000, divided into 140 shares. The company's stated purpose is: “Oppføring av boliger / renovering av bygg, kjøp og salg av fast eiendom og delta i beslektet virksomhet.”.

Former names: BOLIG BYGG AS

Key figures · 2025

Operating profit
NOK −3,000
Equity
NOK −1.3m

Financial health · 2025

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

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

Who owns BOLIG BYGG ÅLESUND AS?

Jan Lillenes
BOLIG BYGG ÅLESUND AS
· NOK −3,000 profit

BOLIG BYGG ÅLESUND AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about BOLIG BYGG ÅLESUND AS

Who owns BOLIG BYGG ÅLESUND AS?

Jan Lillenes is the largest registered owner, with 100.0%.

Who is the general manager of BOLIG BYGG ÅLESUND AS?

Jan Lillenes is registered as general manager of BOLIG BYGG ÅLESUND AS.

Where is BOLIG BYGG ÅLESUND AS based?

BOLIG BYGG ÅLESUND AS has its business address in Vigra.

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.