biztrac. BETA
COMPANY REGISTER PROFILE
990907935 ORG. NO. 2025 ACCOUNTS 10 SECTIONS
Active UPDATED 03.10.2026
Architectural activities

UNODESIGNS AS

Org. no. 990907935 Limited company (AS) Bodø Incorporated 2007 Active
Ownership graph ↗
Operating profit NOK −50,000
Equity NOK 1.2m
Incorporated 2007
Share capital NOK 101,000

Signals

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

UNODESIGNS AS is registered as a limited company in Bodø, Nordland with organisation number 990907935. The business is classified under architectural activities (NACE 71.110). The company was incorporated in 2007. Registered share capital is NOK 101,000, divided into 101 shares. The company's stated purpose is: “Arkitektur og byggprosjektering, arealplanlegging og interiørdesign, samt hva som står i naturlig forbindelse med dette, herunder deltakelse i andre selskaper med lignende virksomhet.”.

Former names: UNO DESIGN & ARKITEKTUR AS, U FURFJORD HOLDING AS

Key figures · 2025

Operating profit
NOK −50,000
▲ +4 %
Equity
NOK 1.2m
▼ −6 %
Est. value
NOK 640,000

Financial health · 2025

Liquidity
17.68
Very good
Current assets ÷ current liabilities
Profitability
0.4%
Not satisfactory
Return on total assets
Solidity
40.7%
Very good
Equity as a share of total capital

Who owns UNODESIGNS AS?

UNODESIGNS AS
· NOK −50,000 profit

UNODESIGNS AS has 1 registered shareholder:

All shareholders and roles →

Which companies does UNODESIGNS AS own?

UNODESIGNS AS holds stakes in 5 companies:

See the full ownership structure →

Frequently asked questions about UNODESIGNS AS

Who owns UNODESIGNS AS?

Unni Johansen Furfjord is the largest registered owner, with 100.0%.

Who is the general manager of UNODESIGNS AS?

Unni Johansen Furfjord is registered as general manager of UNODESIGNS AS.

Where is UNODESIGNS AS based?

UNODESIGNS AS has its business address in Bodø.

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.