BIZTRAC BETA
Civil engineering activities

BYGG & PROSJEKT SERVICE AS

Org. no. 986548831 Limited company (AS) Sandnes Incorporated 2004 Active
Ownership graph ↗
Revenue 2025 NOK 1.7m
Operating profit NOK 29,000
Equity NOK 312,000
Incorporated 2004
Share capital NOK 30,000

BYGG & PROSJEKT SERVICE AS is registered as a limited company in Sandnes, Rogaland with organisation number 986548831. The business is classified under civil engineering activities (NACE 71.121). The company was incorporated in 2004. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Konsulenttjenester til byggebransjen, byggevirksomhet, samt virksomhet i naturlig tilknytning til dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.7m in revenue and NOK 29,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.7m
Operating profit
NOK 29,000
Equity
NOK 312,000
Est. value
NOK 318,000

Financial health · 2025

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

Who owns BYGG & PROSJEKT SERVICE AS?

KJELLAUG KARLSEN POLLESTAD
BYGG & PROSJEKT SERVICE AS
NOK 1.7m rev. · NOK 29,000 profit

BYGG & PROSJEKT SERVICE AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about BYGG & PROSJEKT SERVICE AS

Who owns BYGG & PROSJEKT SERVICE AS?

KJELLAUG KARLSEN POLLESTAD is the largest registered owner, with 95.0%.

What is the revenue of BYGG & PROSJEKT SERVICE AS?

BYGG & PROSJEKT SERVICE AS had revenue of NOK 1.7m in 2025.

Who is the general manager of BYGG & PROSJEKT SERVICE AS?

Kjellaug Karlsen Pollestad is registered as general manager of BYGG & PROSJEKT SERVICE AS.

Where is BYGG & PROSJEKT SERVICE AS based?

BYGG & PROSJEKT SERVICE AS has its business address in Sandnes.

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.