BIZTRAC BETA
COMPANY REGISTER PROFILE
976886631 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 02.09.2026
Construction of residential and non-residential buildings

NESBJØRG AS

Org. no. 976886631 Limited company (AS) Fitjar Incorporated 1996 Active
Ownership graph ↗
Revenue 2025 NOK 909,000
Operating profit NOK 29,000
Equity NOK 3.3m
Incorporated 1996
Share capital NOK 100,000

NESBJØRG AS is registered as a limited company in Fitjar, Vestland with organisation number 976886631. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 1996. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Oppføring og utleie av hus samt tjenesteyting.”. The most recent filed accounts, for the 2025 financial year, show NOK 909,000 in revenue and NOK 29,000 in operating profit.

Key figures · 2025

Revenue
NOK 909,000
▼ −89 %
Operating profit
NOK 29,000
▼ −99 %
Equity
NOK 3.3m
▼ −13 %
Est. value
NOK 3.0m

Financial health · 2025

Liquidity
0.74
Weak
Current assets ÷ current liabilities
Profitability
0.9%
Not satisfactory
Return on total assets
Solidity
83.2%
Very good
Equity as a share of total capital

Who owns NESBJØRG AS?

NESBJØRG AS
NOK 909,000 rev. · NOK 29,000 profit

NESBJØRG AS has 1 registered shareholder:

All shareholders and roles →

Which companies does NESBJØRG AS own?

NESBJØRG AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about NESBJØRG AS

Who owns NESBJØRG AS?

JAN NESBJØRG is the largest registered owner, with 100.0%.

What is the revenue of NESBJØRG AS?

NESBJØRG AS had revenue of NOK 909,000 in 2025.

Who is the general manager of NESBJØRG AS?

Jan Nesbjørg is registered as general manager of NESBJØRG AS.

Where is NESBJØRG AS based?

NESBJØRG AS has its business address in Sagvåg.

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

Report a problem

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