BIZTRAC BETA
Other cleaning activities

HØGNES BYGDESERVICE AS

Org. no. 932150778 Limited company (AS) Lunner Incorporated 2023 Active
Ownership graph ↗
Revenue 2024 NOK 425,000
Operating profit NOK 83,000
Equity NOK 84,000
Incorporated 2023
Share capital NOK 30,000

HØGNES BYGDESERVICE AS is registered as a limited company in Lunner, Akershus with organisation number 932150778. The business is classified under other cleaning activities (NACE 81.230). The company was incorporated in 2023. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Tømrertjenester, skogpleie, brøyteservice og anleggsgartnertjenester, som hage- og landskapsarbeid og annen beslektet virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 425,000 in revenue and NOK 83,000 in operating profit.

Key figures · 2024

Revenue
NOK 425,000
Operating profit
NOK 83,000
Equity
NOK 84,000
Est. value
NOK 302,000

Financial health · 2024

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

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

Who owns HØGNES BYGDESERVICE AS?

LARS HØGNES
HØGNES BYGDESERVICE AS
NOK 425,000 rev. · NOK 83,000 profit

HØGNES BYGDESERVICE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about HØGNES BYGDESERVICE AS

Who owns HØGNES BYGDESERVICE AS?

LARS HØGNES is the largest registered owner, with 100.0%.

What is the revenue of HØGNES BYGDESERVICE AS?

HØGNES BYGDESERVICE AS had revenue of NOK 425,000 in 2024.

Who is the general manager of HØGNES BYGDESERVICE AS?

Lars Høgnes is registered as general manager of HØGNES BYGDESERVICE AS.

Where is HØGNES BYGDESERVICE AS based?

HØGNES BYGDESERVICE AS has its business address in Lunner.

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.