BIZTRAC BETA
Construction of residential and non-residential buildings

RÅHOLT BYGG OG ANLEGG AS

Org. no. 996453146 Limited company (AS) Nord-Odal Incorporated 2011 Active
Ownership graph ↗
Revenue 2024 NOK 2.5m
Operating profit NOK 174,000
Equity NOK 644,000
Incorporated 2011
Share capital NOK 200,000

RÅHOLT BYGG OG ANLEGG AS is registered as a limited company in Nord-Odal, Innlandet with organisation number 996453146. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 2011. Registered share capital is NOK 200,000, divided into 200000 shares. The company's stated purpose is: “Oppføring og vedlikehold av bygg og anlegg for næringsdrivende og private.”. The most recent filed accounts, for the 2024 financial year, show NOK 2.5m in revenue and NOK 174,000 in operating profit.

Key figures · 2024

Revenue
NOK 2.5m
Operating profit
NOK 174,000
Equity
NOK 644,000
Est. value
NOK 936,000

Financial health · 2024

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

Who owns RÅHOLT BYGG OG ANLEGG AS?

PÅL JØRGEN NYMOEN
RÅHOLT BYGG OG ANLEGG AS
NOK 2.5m rev. · NOK 174,000 profit

RÅHOLT BYGG OG ANLEGG AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about RÅHOLT BYGG OG ANLEGG AS

Who owns RÅHOLT BYGG OG ANLEGG AS?

PÅL JØRGEN NYMOEN is the largest registered owner, with 100.0%.

What is the revenue of RÅHOLT BYGG OG ANLEGG AS?

RÅHOLT BYGG OG ANLEGG AS had revenue of NOK 2.5m in 2024.

Who is the general manager of RÅHOLT BYGG OG ANLEGG AS?

Pål Jørgen Nymoen is registered as general manager of RÅHOLT BYGG OG ANLEGG AS.

Where is RÅHOLT BYGG OG ANLEGG AS based?

RÅHOLT BYGG OG ANLEGG AS has its business address in Sagstua.

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.