biztrac. BETA
COMPANY REGISTER PROFILE
921309287 ORG. NO. 2024 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Other personal service activities n.e.c.

NE-RO AS

Org. no. 921309287 Limited company (AS) Nord-Fron Incorporated 2018 Active
Revenue 2024 NOK 154,000
Operating profit NOK 36,000
Equity NOK 567,000
Incorporated 2018
Share capital NOK 30,000

NE-RO AS is registered as a limited company in Nord-Fron, Innlandet with organisation number 921309287. The business is classified under other personal service activities n.e.c. (NACE 96.990). The company was incorporated in 2018. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Selskapets formål skal være diverse innen kokk og servering og vaktmester tjenester.”. The most recent filed accounts, for the 2024 financial year, show NOK 154,000 in revenue and NOK 36,000 in operating profit.

Key figures · 2024

Revenue
NOK 154,000
▼ −46 %
Operating profit
NOK 36,000
▼ −60 %
Equity
NOK 567,000
▲ +5 %
Est. value
NOK 495,000

Financial health · 2024

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

Who owns NE-RO AS?

NE-RO AS
NOK 154,000 rev. · NOK 36,000 profit

NE-RO AS has 1 registered shareholder:

The company is not in the Tax Administration's shareholder register for 2025. The list shows the owners at the end of 2024.

All shareholders and roles →

Frequently asked questions about NE-RO AS

Who owns NE-RO AS?

Lars Espen Skjegstad is the largest registered owner, with 100.0%.

What is the revenue of NE-RO AS?

NE-RO AS had revenue of NOK 154,000 in 2024.

Who is the general manager of NE-RO AS?

Lars Espen Skjegstad is registered as general manager of NE-RO AS.

Where is NE-RO AS based?

NE-RO AS has its business address in Skåbu.

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.