BIZTRAC BETA
Construction of residential and non-residential buildings

GRANÅSEN BYGG AS

Org. no. 998538408 Limited company (AS) Trondheim Incorporated 2012 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −56,000
Equity NOK 1.2m
Incorporated 2012
Share capital NOK 1.1m

Signals

2 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−56k kr).
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

GRANÅSEN BYGG AS is registered as a limited company in Trondheim, Trøndelag with organisation number 998538408. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 2012. Registered share capital is NOK 1.1m, divided into 1100 shares. The company's stated purpose is: “Drive byggevirksomhet, kjøp, utleie og salg av eiendom, samt utvikling og alt som hermed står i forbindelse.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −56,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −56,000
Equity
NOK 1.2m
Est. value
NOK 1.2m

Financial health · 2024

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

Who owns GRANÅSEN BYGG AS?

KENCHA EIENDOM AS
GRANÅSEN BYGG AS
NOK 0 rev. · NOK −56,000 profit

GRANÅSEN BYGG AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about GRANÅSEN BYGG AS

Who owns GRANÅSEN BYGG AS?

KENCHA EIENDOM AS is the largest registered owner, with 100.0%.

What is the revenue of GRANÅSEN BYGG AS?

GRANÅSEN BYGG AS had revenue of NOK 0 in 2024.

Where is GRANÅSEN BYGG AS based?

GRANÅSEN BYGG AS has its business address in Trondheim.

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.