BIZTRAC BETA
Other real estate activities on a fee or contract basis

STAVANGER BYGG OG BOLIGTAKST AS

Org. no. 988935719 Limited company (AS) Randaberg Incorporated 2005 Active
Ownership graph ↗
Revenue 2024 NOK 3.6m
Operating profit NOK 1.1m
Equity NOK 5.0m
Incorporated 2005
Share capital NOK 100,000

STAVANGER BYGG OG BOLIGTAKST AS is registered as a limited company in Randaberg, Rogaland with organisation number 988935719. The business is classified under other real estate activities on a fee or contract basis (NACE 68.320). The company was incorporated in 2005. Registered share capital is NOK 100,000, divided into 1000 shares. The company's stated purpose is: “Bygg-og boligtaksering.”. The most recent filed accounts, for the 2024 financial year, show NOK 3.6m in revenue and NOK 1.1m in operating profit.

Key figures · 2024

Revenue
NOK 3.6m
Operating profit
NOK 1.1m
Equity
NOK 5.0m
Est. value
NOK 6.6m

Financial health · 2024

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

Who owns STAVANGER BYGG OG BOLIGTAKST AS?

GISLE FOSMARK
STAVANGER BYGG OG BOLIGTAKST AS
NOK 3.6m rev. · NOK 1.1m profit

STAVANGER BYGG OG BOLIGTAKST AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about STAVANGER BYGG OG BOLIGTAKST AS

Who owns STAVANGER BYGG OG BOLIGTAKST AS?

GISLE FOSMARK is the largest registered owner, with 100.0%.

What is the revenue of STAVANGER BYGG OG BOLIGTAKST AS?

STAVANGER BYGG OG BOLIGTAKST AS had revenue of NOK 3.6m in 2024.

Who is the general manager of STAVANGER BYGG OG BOLIGTAKST AS?

Gisle Fosmark is registered as general manager of STAVANGER BYGG OG BOLIGTAKST AS.

Where is STAVANGER BYGG OG BOLIGTAKST AS based?

STAVANGER BYGG OG BOLIGTAKST AS has its business address in Randaberg.

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.