biztrac. BETA
COMPANY REGISTER PROFILE
996380513 ORG. NO. 2025 ACCOUNTS 11 SECTIONS
Active UPDATED 03.10.2026
Construction of residential and non-residential buildings

SATS BYGG AS

Org. no. 996380513 Limited company (AS) Frogn Incorporated 2011 Active
Ownership graph ↗
Revenue 2025 NOK 17.4m
Operating profit NOK 469,000
Equity NOK 3.4m
Incorporated 2011
Employees 12
Share capital NOK 100,000

SATS BYGG AS is registered as a limited company in Frogn, Akershus with organisation number 996380513. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 2011 and has 12 registered employees. Registered share capital is NOK 100,000, divided into 100000 shares. The company's stated purpose is: “Snekkerarbeid og oppføring av bygninger samt deltagelse i andre virksomheter med samme formål.”. The most recent filed accounts, for the 2025 financial year, show NOK 17.4m in revenue and NOK 469,000 in operating profit.

Key figures · 2025

Revenue
NOK 17.4m
▼ −21 %
Operating profit
NOK 469,000
▼ −62 %
Equity
NOK 3.4m
▲ +14 %
Est. value
NOK 3.6m

Financial health · 2025

Liquidity
1.52
Good
Current assets ÷ current liabilities
Profitability
8.9%
Satisfactory
Return on total assets
Solidity
59.3%
Very good
Equity as a share of total capital

Who owns SATS BYGG AS?

SATS BYGG AS
NOK 17.4m rev. · NOK 469,000 profit

SATS BYGG AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about SATS BYGG AS

Who owns SATS BYGG AS?

Stian Hulbach is the largest registered owner, with 50.0%.

What is the revenue of SATS BYGG AS?

SATS BYGG AS had revenue of NOK 17.4m in 2025.

Who is the general manager of SATS BYGG AS?

Stian Hulbach is registered as general manager of SATS BYGG AS.

Where is SATS BYGG AS based?

SATS BYGG AS has its business address in Drøbak.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.