BIZTRAC BETA
COMPANY REGISTER PROFILE
921761252 ORG. NO. 2024 ACCOUNTS 7 SECTIONS
Active UPDATED 15.06.2026
Site preparation

BØHAGEN HYTTE OG BYGDE SERVISE AS

Org. no. 921761252 Limited company (AS) Nord-Aurdal Incorporated 2018 Active
Ownership graph ↗
Revenue 2024 NOK 172,000
Operating profit NOK 30,000
Equity NOK 334,000
Incorporated 2018
Share capital NOK 30,000

BØHAGEN HYTTE OG BYGDE SERVISE AS is registered as a limited company in Nord-Aurdal, Innlandet with organisation number 921761252. The business is classified under site preparation (NACE 43.120). The company was incorporated in 2018. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Graving, brøyting, enkel snekring, maling og beising, hytte- og husvask og div. hjelp.”. The most recent filed accounts, for the 2024 financial year, show NOK 172,000 in revenue and NOK 30,000 in operating profit.

Key figures · 2024

Revenue
NOK 172,000
Operating profit
NOK 30,000
Equity
NOK 334,000
Est. value
NOK 231,000

Financial health · 2024

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

Who owns BØHAGEN HYTTE OG BYGDE SERVISE AS?

HELGA GURI HAGEBRÅTEN-NYHUUS
BØHAGEN HYTTE OG BYGDE SERVISE AS
NOK 172,000 rev. · NOK 30,000 profit

BØHAGEN HYTTE OG BYGDE SERVISE AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about BØHAGEN HYTTE OG BYGDE SERVISE AS

Who owns BØHAGEN HYTTE OG BYGDE SERVISE AS?

HELGA GURI HAGEBRÅTEN-NYHUUS is the largest registered owner, with 95.0%.

What is the revenue of BØHAGEN HYTTE OG BYGDE SERVISE AS?

BØHAGEN HYTTE OG BYGDE SERVISE AS had revenue of NOK 172,000 in 2024.

Where is BØHAGEN HYTTE OG BYGDE SERVISE AS based?

BØHAGEN HYTTE OG BYGDE SERVISE AS has its business address in Ulnes.

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.