BIZTRAC BETA
Construction of residential and non-residential buildings

ADMOS BYGG AS

Org. no. 925297372 Limited company (AS) Sogndal Incorporated 2020 Active
Ownership graph ↗
Revenue 2025 NOK 3.2m
Operating profit NOK −864,000
Equity NOK 1.3m
Incorporated 2020
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−864k kr).

ADMOS BYGG AS is registered as a limited company in Sogndal, Vestland with organisation number 925297372. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 2020. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Tømrer, betong og malervirksomhet inklusive varesalg uten fast utsalgssted, samt oppføring, investering og utleie av bygg.”. The most recent filed accounts, for the 2025 financial year, show NOK 3.2m in revenue and NOK −864,000 in operating profit.

Key figures · 2025

Revenue
NOK 3.2m
Operating profit
NOK −864,000
Equity
NOK 1.3m
Est. value
NOK 1.7m

Financial health · 2025

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

Who owns ADMOS BYGG AS?

ADRIAN PATRYK MOSCINSKI
ADMOS BYGG AS
NOK 3.2m rev. · NOK −864,000 profit

ADMOS BYGG AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about ADMOS BYGG AS

Who owns ADMOS BYGG AS?

ADRIAN PATRYK MOSCINSKI is the largest registered owner, with 100.0%.

What is the revenue of ADMOS BYGG AS?

ADMOS BYGG AS had revenue of NOK 3.2m in 2025.

Who is the general manager of ADMOS BYGG AS?

Adrian Patryk Moscinski is registered as general manager of ADMOS BYGG AS.

Where is ADMOS BYGG AS based?

ADMOS BYGG AS has its business address in Sogndal.

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.