BIZTRAC BETA
Joinery installation

SÆBØ BYGG & INTERIØR AS

Org. no. 986041230 Limited company (AS) Bergen Incorporated 2003 Active
Ownership graph ↗
Revenue 2024 NOK 22.6m
Operating profit NOK −2.6m
Equity NOK 2.8m
Incorporated 2003
Employees 21
Share capital NOK 100,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−2,6 mill kr).

SÆBØ BYGG & INTERIØR AS is registered as a limited company in Bergen, Vestland with organisation number 986041230. The business is classified under joinery installation (NACE 43.320). The company was incorporated in 2003 and has 21 registered employees. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Snekkerarbeid, rehabilitering av bygg og dermed beslektet virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 22.6m in revenue and NOK −2.6m in operating profit.

Key figures · 2024

Revenue
NOK 22.6m
Operating profit
NOK −2.6m
Equity
NOK 2.8m
Est. value
NOK 9.1m

Financial health · 2024

Liquidity
1.49
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
35.8%
Good
Equity as a share of total capital

Who owns SÆBØ BYGG & INTERIØR AS?

TOM NORVAL SÆBØ
SÆBØ BYGG & INTERIØR AS
NOK 22.6m rev. · NOK −2.6m profit

SÆBØ BYGG & INTERIØR AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about SÆBØ BYGG & INTERIØR AS

Who owns SÆBØ BYGG & INTERIØR AS?

TOM NORVAL SÆBØ is the largest registered owner, with 100.0%.

What is the revenue of SÆBØ BYGG & INTERIØR AS?

SÆBØ BYGG & INTERIØR AS had revenue of NOK 22.6m in 2024.

Who is the general manager of SÆBØ BYGG & INTERIØR AS?

Tom Norval Sæbø is registered as general manager of SÆBØ BYGG & INTERIØR AS.

Where is SÆBØ BYGG & INTERIØR AS based?

SÆBØ BYGG & INTERIØR AS has its business address in Nesttun.

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.