BIZTRAC BETA
Development of building projects

BISPEBRYGGEN AS

Org. no. 968630083 Limited company (AS) Stavanger Incorporated 1994 Active
Ownership graph ↗
Revenue 2024 NOK 2.2m
Operating profit NOK 1.8m
Equity NOK −26.6m
Incorporated 1994
Share capital NOK 150,000

Signals

1 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−26,6 mill kr).

BISPEBRYGGEN AS is registered as a limited company in Stavanger, Rogaland with organisation number 968630083. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 1994. Registered share capital is NOK 150,000. The company's stated purpose is: “Eie, utvikle og å drive fast eiendom, samt å delta i andre selskaper.”. The most recent filed accounts, for the 2024 financial year, show NOK 2.2m in revenue and NOK 1.8m in operating profit.

Key figures · 2024

Revenue
NOK 2.2m
Operating profit
NOK 1.8m
Equity
NOK −26.6m
Est. value
NOK 11.0m

Financial health · 2024

Liquidity
0.33
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-402.7%
Weak
Equity as a share of total capital

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

Who owns BISPEBRYGGEN AS?

KARK AS
BISPEBRYGGEN AS
NOK 2.2m rev. · NOK 1.8m profit

BISPEBRYGGEN AS has 1 registered shareholder:

All shareholders and roles →

Group structure

BISPEBRYGGEN AS er morselskap for 2 datterselskaper:

Frequently asked questions about BISPEBRYGGEN AS

Who owns BISPEBRYGGEN AS?

KARK AS is the largest registered owner, with 100.0%.

What is the revenue of BISPEBRYGGEN AS?

BISPEBRYGGEN AS had revenue of NOK 2.2m in 2024.

Who is the general manager of BISPEBRYGGEN AS?

Kåre Vierdal is registered as general manager of BISPEBRYGGEN AS.

Where is BISPEBRYGGEN AS based?

BISPEBRYGGEN AS has its business address in Stavanger.

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.