BIZTRAC BETA
Other specialised construction activities n.e.c.

TAULE BETONGBYGG AS

Org. no. 924414804 Limited company (AS) Gloppen Incorporated 2020 Active
Ownership graph ↗
Revenue 2025 NOK 1.0m
Operating profit NOK −83,000
Equity NOK 475,000
Incorporated 2020
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−83k kr).

TAULE BETONGBYGG AS is registered as a limited company in Gloppen, Vestland with organisation number 924414804. The business is classified under other specialised construction activities n.e.c. (NACE 43.990). The company was incorporated in 2020. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Drive med betong og bygningsarbeid med sal av dertilhøyrande varer og tjenester.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.0m in revenue and NOK −83,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.0m
Operating profit
NOK −83,000
Equity
NOK 475,000
Est. value
NOK 564,000

Financial health · 2025

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

Who owns TAULE BETONGBYGG AS?

GEIR OVE TAULE
TAULE BETONGBYGG AS
NOK 1.0m rev. · NOK −83,000 profit

TAULE BETONGBYGG AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about TAULE BETONGBYGG AS

Who owns TAULE BETONGBYGG AS?

GEIR OVE TAULE is the largest registered owner, with 100.0%.

What is the revenue of TAULE BETONGBYGG AS?

TAULE BETONGBYGG AS had revenue of NOK 1.0m in 2025.

Who is the general manager of TAULE BETONGBYGG AS?

Geir Ove Taule is registered as general manager of TAULE BETONGBYGG AS.

Where is TAULE BETONGBYGG AS based?

TAULE BETONGBYGG AS has its business address in Sandane.

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.