BIZTRAC BETA
Civil engineering activities

WALBY BYGG & TAKST AS

Org. no. 931457217 Limited company (AS) Fredrikstad Incorporated 2023 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −3,000
Equity NOK 42,000
Incorporated 2023
Share capital NOK 50,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−3k kr).

WALBY BYGG & TAKST AS is registered as a limited company in Fredrikstad, Østfold with organisation number 931457217. The business is classified under civil engineering activities (NACE 71.121). The company was incorporated in 2023. Registered share capital is NOK 50,000, divided into 50000 shares. The company's stated purpose is: “Taksering og konsulenttjenester innen bygg og eiendom.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −3,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −3,000
Equity
NOK 42,000
Est. value
NOK 68,000

Financial health · 2024

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

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

Who owns WALBY BYGG & TAKST AS?

GJERMUND WALBY
WALBY BYGG & TAKST AS
NOK 0 rev. · NOK −3,000 profit

WALBY BYGG & TAKST AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about WALBY BYGG & TAKST AS

Who owns WALBY BYGG & TAKST AS?

GJERMUND WALBY is the largest registered owner, with 100.0%.

What is the revenue of WALBY BYGG & TAKST AS?

WALBY BYGG & TAKST AS had revenue of NOK 0 in 2024.

Who is the general manager of WALBY BYGG & TAKST AS?

Gjermund Walby is registered as general manager of WALBY BYGG & TAKST AS.

Where is WALBY BYGG & TAKST AS based?

WALBY BYGG & TAKST AS has its business address in Fredrikstad.

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.