BIZTRAC BETA
Rental and operating of own or leased real estate

NORBY OG STEINNES AS

Org. no. 889101822 Limited company (AS) Oslo Incorporated 2005 Active
Ownership graph ↗
Revenue 2024 NOK 1.4m
Operating profit NOK 748,000
Equity NOK 13.1m
Incorporated 2005
Share capital NOK 108,000

NORBY OG STEINNES AS is registered as a limited company in Oslo, Oslo with organisation number 889101822. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2005. Registered share capital is NOK 108,000, divided into 2160 shares. The company's stated purpose is: “Kjøp, salg og drift av fast eiendom, biler, båter og investering i selskaper som driver slik virksomhet, samt investering i verdipapirer og aksjer/andeler i annen virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 1.4m in revenue and NOK 748,000 in operating profit.

Key figures · 2024

Revenue
NOK 1.4m
Operating profit
NOK 748,000
Equity
NOK 13.1m
Est. value
NOK 11.1m

Financial health · 2024

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

Who owns NORBY OG STEINNES AS?

AUDNY STEINNES
NORBY OG STEINNES AS
NOK 1.4m rev. · NOK 748,000 profit

NORBY OG STEINNES AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about NORBY OG STEINNES AS

Who owns NORBY OG STEINNES AS?

AUDNY STEINNES is the largest registered owner, with 100.0%.

What is the revenue of NORBY OG STEINNES AS?

NORBY OG STEINNES AS had revenue of NOK 1.4m in 2024.

Who is the general manager of NORBY OG STEINNES AS?

Audny Steinnes is registered as general manager of NORBY OG STEINNES AS.

Where is NORBY OG STEINNES AS based?

NORBY OG STEINNES AS has its business address in Oslo.

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.