BIZTRAC BETA
Construction of residential and non-residential buildings

KRANGNES BYGG AS

Org. no. 930339172 Limited company (AS) Hitra Incorporated 2022 Active
Ownership graph ↗
Revenue 2025 NOK 27.0m
Operating profit NOK 4.1m
Equity NOK 11.6m
Incorporated 2022
Employees 10
Share capital NOK 100,000

KRANGNES BYGG AS is registered as a limited company in Hitra, Trøndelag with organisation number 930339172. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 2022 and has 10 registered employees. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Oppføring av nye- og renovering av eldre bygninger, samt tilhørende aktiviteter som naturlig faller sammen med dette. Selskapet kan delta i andre selskaper.”. The most recent filed accounts, for the 2025 financial year, show NOK 27.0m in revenue and NOK 4.1m in operating profit.

Key figures · 2025

Revenue
NOK 27.0m
Operating profit
NOK 4.1m
Equity
NOK 11.6m
Est. value
NOK 18.6m

Financial health · 2025

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

Who owns KRANGNES BYGG AS?

T KRANGNES HOLDING AS
KRANGNES BYGG AS
NOK 27.0m rev. · NOK 4.1m profit

KRANGNES BYGG AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about KRANGNES BYGG AS

Who owns KRANGNES BYGG AS?

T KRANGNES HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of KRANGNES BYGG AS?

KRANGNES BYGG AS had revenue of NOK 27.0m in 2025.

Who is the general manager of KRANGNES BYGG AS?

Torstein Krangnes is registered as general manager of KRANGNES BYGG AS.

Where is KRANGNES BYGG AS based?

KRANGNES BYGG AS has its business address in Ansnes.

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.