BIZTRAC BETA
Construction of residential and non-residential buildings

AUDNA BYGG AS

Org. no. 999042589 Limited company (AS) Lindesnes Incorporated 2012 Active
Ownership graph ↗
Revenue 2024 NOK 17.7m
Operating profit NOK 1.1m
Equity NOK 1.4m
Incorporated 2012
Employees 9
Share capital NOK 600,000

Signals

1 flags
  • Nylig endring 2026-06-23 Adresseendring registrert 2026-06-23.

AUDNA BYGG AS is registered as a limited company in Lindesnes, Agder with organisation number 999042589. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 2012 and has 9 registered employees. Registered share capital is NOK 600,000, divided into 1080 shares. The company's stated purpose is: “Salg av byggetjenester samt alt hva hermed står i forbindelse, rådgivning og deltagelse i andre virksomheter.”. The most recent filed accounts, for the 2024 financial year, show NOK 17.7m in revenue and NOK 1.1m in operating profit.

Key figures · 2024

Revenue
NOK 17.7m
Operating profit
NOK 1.1m
Equity
NOK 1.4m
Est. value
NOK 3.8m

Financial health · 2024

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

Who owns AUDNA BYGG AS?

KIM MARIUS HOMESTAD SKULAND
AUDNA BYGG AS
NOK 17.7m rev. · NOK 1.1m profit

AUDNA BYGG AS has 5 registered shareholders:

All shareholders and roles →

Frequently asked questions about AUDNA BYGG AS

Who owns AUDNA BYGG AS?

KIM MARIUS HOMESTAD SKULAND is the largest registered owner, with 20.0%.

What is the revenue of AUDNA BYGG AS?

AUDNA BYGG AS had revenue of NOK 17.7m in 2024.

Who is the general manager of AUDNA BYGG AS?

Thomas Støle Fidje is registered as general manager of AUDNA BYGG AS.

Where is AUDNA BYGG AS based?

AUDNA BYGG AS has its business address in Lindesnes.

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.