BIZTRAC BETA
Construction of residential and non-residential buildings

ALT BYGG AS

Org. no. 964217157 Limited company (AS) Trondheim Incorporated 1992 Active
Ownership graph ↗
Revenue 2025 NOK 3.1m
Operating profit NOK 2.0m
Equity NOK −1.5m
Incorporated 1992
Share capital NOK 1.2m

Signals

1 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−1,5 mill kr).

ALT BYGG AS is registered as a limited company in Trondheim, Trøndelag with organisation number 964217157. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 1992. Registered share capital is NOK 1.2m, divided into 40 shares. The company's stated purpose is: “Virksomhet innen bygg og anlegg, nybygg, rehabili- tering og levering av varer samt deltagelse i andre selskaper.”. The most recent filed accounts, for the 2025 financial year, show NOK 3.1m in revenue and NOK 2.0m in operating profit.

Key figures · 2025

Revenue
NOK 3.1m
Operating profit
NOK 2.0m
Equity
NOK −1.5m
Est. value
NOK 10.2m

Financial health · 2025

Liquidity
2.74
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-65.8%
Weak
Equity as a share of total capital

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

Who owns ALT BYGG AS?

FRANK OTTO GJERDE
ALT BYGG AS
NOK 3.1m rev. · NOK 2.0m profit

ALT BYGG AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about ALT BYGG AS

Who owns ALT BYGG AS?

FRANK OTTO GJERDE is the largest registered owner, with 100.0%.

What is the revenue of ALT BYGG AS?

ALT BYGG AS had revenue of NOK 3.1m in 2025.

Who is the general manager of ALT BYGG AS?

Frank Otto Gjerde is registered as general manager of ALT BYGG AS.

Where is ALT BYGG AS based?

ALT BYGG AS has its business address in Ranheim.

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.