BIZTRAC BETA
Construction of residential and non-residential buildings

GAULIN BYGG AS

Org. no. 970986049 Limited company (AS) Sarpsborg Incorporated 1994 Active
Ownership graph ↗
Revenue 2024 NOK 9.6m
Operating profit NOK 888,000
Equity NOK 2.7m
Incorporated 1994
Employees 7
Share capital NOK 50,000

GAULIN BYGG AS is registered as a limited company in Sarpsborg, Østfold with organisation number 970986049. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 1994 and has 7 registered employees. Registered share capital is NOK 50,000, divided into 50 shares. The company's stated purpose is: “Byggevirksomhet samt kjøp og salg av bygge- materialer. Videre ved aksjebesittelse eller på annen måte gjøre seg interessert i selskaper med samme eller lignende formål.”. The most recent filed accounts, for the 2024 financial year, show NOK 9.6m in revenue and NOK 888,000 in operating profit.

Key figures · 2024

Revenue
NOK 9.6m
Operating profit
NOK 888,000
Equity
NOK 2.7m
Est. value
NOK 4.1m

Financial health · 2024

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

Who owns GAULIN BYGG AS?

GEIR HÅKON GAULIN
GAULIN BYGG AS
NOK 9.6m rev. · NOK 888,000 profit

GAULIN BYGG AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about GAULIN BYGG AS

Who owns GAULIN BYGG AS?

GEIR HÅKON GAULIN is the largest registered owner, with 100.0%.

What is the revenue of GAULIN BYGG AS?

GAULIN BYGG AS had revenue of NOK 9.6m in 2024.

Who is the general manager of GAULIN BYGG AS?

Geir Håkon Gaulin is registered as general manager of GAULIN BYGG AS.

Where is GAULIN BYGG AS based?

GAULIN BYGG AS has its business address in Skjeberg.

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.